From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] systemd: build failure against pam on arm
Date: Mon, 25 Dec 2017 16:13:37 +0100 [thread overview]
Message-ID: <20171225151337.GC27558@waldemar-brodkorb.de> (raw)
In-Reply-To: <87po73d1xz.fsf@paral.in>
Hi,
Christian Stewart wrote,
> Hi Waldemar,
>
> There are no extra pam files in my Buildroot tree - before building I
> ensure this with a "git clean -xfd" and I've searched the tree as well.
But that is strange then.
find . -name libpam_misc.so\*
./output/build/linux-pam-1.3.0/libpam_misc/.libs/libpam_misc.so.0
./output/build/linux-pam-1.3.0/libpam_misc/.libs/libpam_misc.so
./output/build/linux-pam-1.3.0/libpam_misc/.libs/libpam_misc.so.0.82.1
./output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/libpam_misc.so.0
./output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/libpam_misc.so
./output/host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/libpam_misc.so.0.82.1
./output/target/usr/lib/libpam_misc.so.0
./output/target/usr/lib/libpam_misc.so
./output/target/usr/lib/libpam_misc.so.0.82.1
Systemd wants to find libpam, if it is not there it seems to
fallback to your native libpam.
You should always run "make clean && make" if you make any
changes to your .config.
best regards
Waldemar
next prev parent reply other threads:[~2017-12-25 15:13 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
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 [this message]
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=20171225151337.GC27558@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.