From: Christian Stewart <christian@paral.in>
To: buildroot@busybox.net
Subject: [Buildroot] systemd: build failure against pam on arm
Date: Tue, 19 Dec 2017 15:26:53 -0800 [thread overview]
Message-ID: <87lghy2taa.fsf@paral.in> (raw)
In-Reply-To: <29DD8155-F769-488E-8A9E-39D8B6D18B54@openadk.org>
Hi Waldemar, all,
Waldemar Brodkorb <wbx@openadk.org> writes:
> can you make the last failing link command more verbose?
> CCLD should be expanded to the full command used.
I'm still seeing this error under Gentoo against 2017.11:
>>> systemd 234 Building
PATH="/buildroot/host/bin:/buildroot/host/sbin:/usr/x86_64-pc-linux-gnu/gcc-bin/6.4.0:/usr/local/bin:/usr/bin:/bin:/opt/bin:/opt/golang/bin /usr/bin/make -j5 -C /buildroot/build/systemd-234/
Making all in .
CCLD libnss_systemd.la
CCLD libnss_myhostname.la
CCLD systemd-cgtop
CCLD systemd-cgls
CCLD systemd-nspawn
CCLD systemd-detect-virt
CCLD systemd-delta
CCLD systemd-analyze
CCLD systemd-run
CCLD systemd-mount
CCLD systemd-stdio-bridge
CCLD systemd-path
CCLD busctl
CCLD systemd-socket-activate
/lib/libpam.so: file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
I believe on Gentoo some sort of environment leakage is breaking the lib path.
defconfig:
BR2_arm=y
BR2_cortex_a9=y
BR2_ARM_ENABLE_NEON=y
BR2_ARM_ENABLE_VFP=y
BR2_ARM_INSTRUCTIONS_THUMB2=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_INIT_SYSTEMD=y
This has been an issue for quite some time, and the reason why I have
not upgraded past the early 2017 release. I finally upgraded to 2017.11
and have found that it's once again broken compilations on my machine.
I'm not sure how to get Buildroot to produce a more verbose CCLD output,
I have tried "make VERBOSE=1" but this doesn't give me more than shown above.
I previously bisected the issue down to commit 400eaa3452 if that helps.
That commit bumped the linux headers (I believe) from 4.9.9 to 4.10.0.
Best,
Christian Stewart
next prev parent reply other threads:[~2017-12-19 23:26 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 [this message]
2017-12-20 0:31 ` Christian Stewart
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=87lghy2taa.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