All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] systemd: build failure against pam on arm
Date: Fri, 02 Jun 2017 00:03:14 +0200	[thread overview]
Message-ID: <87fufjgycd.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CA+h8R2q1W9PZ8DbTDuxZQhg3+hauZqaDdwzFAGgmTJd7KqiQEg@mail.gmail.com> (Christian Stewart's message of "Wed, 31 May 2017 19:29:11 -0700")

>>>>> "Christian" == Christian Stewart <christian@paral.in> writes:

 > Hi all,
 > Compiling against 2017.05, with the following defconfig:

 > BR2_arm=y
 > BR2_cortex_a15=y
 > BR2_ARM_FPU_NEON_VFPV4=y
 > BR2_OPTIMIZE_2=y
 > BR2_TOOLCHAIN_EXTERNAL=y
 > BR2_INIT_SYSTEMD=y
 > # BR2_TARGET_ROOTFS_TAR is not set
 > BR2_PACKAGE_LINUX_PAM=y

 > I get this error consistently during the systemd compilation when PAM
 > is enabled:

 > /output/host/opt/ext-toolchain/bin/../lib/gcc/arm-linux-gnueabihf/6.3.1/../../../../arm-linux-gnueabihf/bin/ld.gold:
 > error: /lib/libpam.so: incompatible target
 > /output/host/opt/ext-toolchain/bin/../lib/gcc/arm-linux-gnueabihf/6.3.1/../../../../arm-linux-gnueabihf/bin/ld.gold:
 > error: /lib/libpam_misc.so: incompatible target
 > collect2: error: ld returned 1 exit status

 > It looks like it's attempting to link against /lib/libpam.so from my system.

Can you paste a few more lines above this error?

I cannot reproduce it here, not even after install libpam0g-dev on my
build host.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2017-06-01 22:03 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 [this message]
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
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=87fufjgycd.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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.