All of lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] systemd: build failure against pam on arm
Date: Thu, 28 Dec 2017 19:04:03 +0100	[thread overview]
Message-ID: <20171228180402.GR27558@waldemar-brodkorb.de> (raw)
In-Reply-To: <87o9mkdlf1.fsf@paral.in>

Hi Christian,
Christian Stewart wrote,

> Sure. To make things less ambiguous, here is exactly what I did to produce
> these new results in this email:
> 
>  $ cd ~/Documents
>  $ git clone git://git.busybox.net/buildroot buildroot
>  $ cd buildroot && git checkout 2017.11
>  $ cp ~/Notes/buildroot-pam/defconfig ./defconfig
>  $ make defconfig BR2_DEFCONFIG=defconfig
>  $ make # build fails on systemd
>  $ rm -rf output/build/systemd*
>  $ make V=1 BR2_JOBS=1 &>systemd-fail.log
>  $ tar -cvf systemd-fail.tar.gz ./output/build/systemd*
> 
> > Can you do rm -rf output/build/systemd* && make V=1 &>log
> > And sent me the log and the systemd build directory for post-mortem
> > analysis.
> 
> Attached are defconfig and systemd-fail.log. The archive is too big, so
> I uploaded it to Google Drive, available here:
> 
> https://drive.google.com/a/aperturerobotics.com/file/d/1Sxq-5smjUFntRCe0o9zIYs6_--dxjjGA/view?usp=sharing
> 
> Thank you again for taking the time to debug this, I've had this issue
> early 2017 and have avoided upgrading Buildroot until we find a fix.

Sorry I believe you entered the world of libtool hell.

For the hardcore buildroot hackers, if you create a symlink in /lib
pointing to libpam.so / libpam_misc.so you can reproduce the issue.

By the way, I couldn't reproduce the issue with OpenADK.
Unfortunately I can't point to a specific patch. 
I always pass -Wl,-rpath-link -Wl,$(STAGING_DIR)/usr/lib in
LDFLAGS and I always remove any .la files from staging directory.

I do not patch the package provided ltmain.sh/libtool stuff like
Buildroot, but I always use libtool 2.4.6 with a small patch 
like this when autoreconfing a package:
+++ libtool-2.4.6/m4/libtool.m4
-  _LT_TAGVAR(hardcode_automatic, $1)=no
+  _LT_TAGVAR(hardcode_automatic, $1)=yes
 
So sorry, I can't help you out of the hell.

best regards
 Waldemar

  parent reply	other threads:[~2017-12-28 18:04 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
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 [this message]
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=20171228180402.GR27558@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.