From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2017-02-26: libsidplay issue on PowerPC64
Date: Mon, 27 Feb 2017 23:38:18 +0100 [thread overview]
Message-ID: <20170227233818.1300436b@free-electrons.com> (raw)
In-Reply-To: <20170227142854.34d3fb86@free-electrons.com>
Hello,
On Mon, 27 Feb 2017 14:28:54 +0100, Thomas Petazzoni wrote:
> > powerpc64le | libsidplay2-2.1.1 | NOK | http://autobuild.buildroot.net/results/caba78cc2706accc187a428364c0e0d10a1dcd60
>
> Missing -fPIC apparently. Sam?
I had a closer look at this one. What happens is:
1. libsidplay is autoreconf'ed due to <pkg>_AUTORECONF = YES
2. we apply the powerpc64le trick that patches the configure script,
thanks to this, during the configure step, the fact that shared
libraries are supported is properly detected.
3. for some reason, when the build starts, it auto-autoreconfs itself,
which rewrites the configure script, without the powerpc64le
trick. ./configure is re-executed, and this time doesn't detected
shared library support anymore.
So the issue is: why does the package decides to auto-autoreconf itself
at the beginning of the build step.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-27 22:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-26 Thomas Petazzoni
2017-02-27 13:28 ` [Buildroot] Analysis of build " Thomas Petazzoni
2017-02-27 15:54 ` Yann E. MORIN
2017-02-27 15:57 ` Thomas Petazzoni
2017-02-27 16:54 ` Frank Hunleth
2017-02-27 20:20 ` Thomas Petazzoni
2017-02-27 22:38 ` Thomas Petazzoni [this message]
2017-02-28 0:41 ` [Buildroot] Analysis of build results for 2017-02-26: libsidplay issue on PowerPC64 Sam Bobroff
2017-02-27 22:38 ` [Buildroot] Analysis of build results for 2017-02-26: classpath issue Thomas Petazzoni
2017-02-27 23:01 ` [Buildroot] Analysis of build results for 2017-02-26: librsvg failure Thomas Petazzoni
2017-02-28 9:00 ` Peter Korsgaard
2017-02-28 9:05 ` Thomas Petazzoni
2017-02-28 14:16 ` Thomas Petazzoni
2017-02-28 14:48 ` Peter Korsgaard
2017-02-28 15:37 ` Thomas Petazzoni
2017-02-28 16:10 ` Peter Korsgaard
2017-02-28 15:34 ` [Buildroot] Analysis of build results for 2017-02-26 Vlad Zakharov
2017-02-28 16:02 ` Thomas Petazzoni
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=20170227233818.1300436b@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox