From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] systemd: build failure against pam on arm
Date: Sun, 24 Dec 2017 11:38:03 +0100 [thread overview]
Message-ID: <20171224103803.GW27558@waldemar-brodkorb.de> (raw)
In-Reply-To: <873741w59p.fsf@paral.in>
Hi,
Christian Stewart wrote,
> Hi Waldemar,
>
> Thank you for looking into this-
>
> Waldemar Brodkorb <wbx@openadk.org> writes:
> > check config.log where pam_misc is added. May be configure has a bug and detects your host pam under certain conditions.
>
> Seems like it.
>
> > PAM_LIBS='-lpam -lpam_misc'
>
Is there a copy of libpam_misc.so somewhere in your buildroot
directory?
best regards
Waldemar
next prev parent reply other threads:[~2017-12-24 10:38 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 [this message]
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=20171224103803.GW27558@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox