From mboxrd@z Thu Jan  1 00:00:00 1970
From: Waldemar Brodkorb <wbx@openadk.org>
Date: Wed, 14 Feb 2018 05:57:00 +0100
Subject: [Buildroot] systemd: build failure against pam on arm
In-Reply-To: <87wozgz3df.fsf@paral.in>
References: <20171225151337.GC27558@waldemar-brodkorb.de>
 <87mv25cg5t.fsf@paral.in> <87shbxq99x.fsf@paral.in>
 <20171227030548.GE27558@waldemar-brodkorb.de>
 <87y3loenlr.fsf@paral.in>
 <20171227080520.GF27558@waldemar-brodkorb.de>
 <87o9mkdlf1.fsf@paral.in>
 <20171228180402.GR27558@waldemar-brodkorb.de>
 <874lo9xqb7.fsf@paral.in> <87wozgz3df.fsf@paral.in>
Message-ID: <20180214045700.GH12535@waldemar-brodkorb.de>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

Hi,
Christian Stewart wrote,

> Hi Waldemar, all,
> 
> 
> Christian Stewart <christian@paral.in> writes:
> > Waldemar Brodkorb <wbx@openadk.org> writes:
> >>> 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.
> 
> It appears that this bug is fixed in the latest release (2018.02 rc2).

Sure, a nice side effect of the switch to meson by upstream, which eliminates
libtool ;)

best regards
 Waldemar