From: Christian Stewart <christian@paral.in>
To: buildroot@busybox.net
Subject: [Buildroot] systemd: build failure against pam on arm
Date: Tue, 19 Dec 2017 16:31:55 -0800 [thread overview]
Message-ID: <878tdy2q9w.fsf@paral.in> (raw)
In-Reply-To: <87lghy2taa.fsf@paral.in>
Hi all,
Christian Stewart <christian@paral.in> writes:
> I'm still seeing this error under Gentoo against 2017.11:
> CCLD busctl
> CCLD systemd-socket-activate
> /lib/libpam.so: file not recognized: File format not recognized
> collect2: error: ld returned 1 exit status
>
> defconfig:
I have found that the defconfig I sent in my previous email does not
reproduce the issue. The issue can successfully be reproduced against
2017.11 with the following defconfig:
BR2_arm=y
BR2_cortex_a7=y
BR2_ARM_FPU_NEON_VFPV4=y
BR2_CCACHE=y
BR2_OPTIMIZE_2=y
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_9=y
BR2_BINUTILS_VERSION_2_27_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_GCC_ENABLE_LTO=y
BR2_INIT_SYSTEMD=y
BR2_SYSTEM_BIN_SH_BASH=y
BR2_ENABLE_LOCALE_WHITELIST="C en_US en_US.UTF-8"
BR2_GENERATE_LOCALE="en_US.UTF-8"
BR2_PACKAGE_BUSYBOX_SELINUX=y
I'm not sure what it is in this set of config options that causes the problem.
Best,
Christian Stewart
next prev parent reply other threads:[~2017-12-20 0:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 2:29 [Buildroot] systemd: build failure against pam on arm Christian Stewart
2017-06-01 18:36 ` Christian Stewart
2017-06-01 22:03 ` Peter Korsgaard
2017-06-01 23:35 ` Christian Stewart
2017-06-03 2:48 ` Christian Stewart
2017-06-03 10:54 ` Waldemar Brodkorb
2017-12-19 23:26 ` Christian Stewart
2017-12-20 0:31 ` Christian Stewart [this message]
2017-12-23 7:25 ` Christian Stewart
2017-12-23 10:06 ` Waldemar Brodkorb
2017-12-23 20:36 ` Christian Stewart
2017-12-24 10:38 ` Waldemar Brodkorb
2017-12-24 12:09 ` Waldemar Brodkorb
2017-12-25 1:35 ` Christian Stewart
2017-12-25 15:13 ` Waldemar Brodkorb
2017-12-26 21:50 ` Christian Stewart
2017-12-27 0:55 ` Christian Stewart
2017-12-27 3:05 ` Waldemar Brodkorb
2017-12-27 5:39 ` Christian Stewart
2017-12-27 8:05 ` Waldemar Brodkorb
[not found] ` <87o9mkdlf1.fsf@paral.in>
2017-12-28 18:04 ` Waldemar Brodkorb
2017-12-29 19:54 ` Christian Stewart
2018-02-14 2:55 ` Christian Stewart
2018-02-14 4:57 ` Waldemar Brodkorb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878tdy2q9w.fsf@paral.in \
--to=christian@paral.in \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox