From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2017-02-13
Date: Wed, 15 Feb 2017 09:37:23 +0100 [thread overview]
Message-ID: <20170215093723.00b3d499@free-electrons.com> (raw)
In-Reply-To: <20170215024549.GA25646@tungsten.ozlabs.ibm.com>
Hello,
On Wed, 15 Feb 2017 13:45:49 +1100, Sam Bobroff wrote:
> > > powerpc64 | libsvg-0.1.4 | NOK | http://autobuild.buildroot.net/results/f2d5b2459080bf9c67906b8b240150303bb61461
> >
> > /usr/lib64/libexpat.so: error adding symbols: File in wrong format
> > collect2: error: ld returned 1 exit status
> >
> > It's picking some host library, which is wrong. Carsten, you're listed
> > in the DEVELOPERS file for libsvg, could you have a look?
>
> I've had a look at this, it seems to be that pkg-config is used to
> locate libxml, but when expat is used instead it just adds '-lexpat' --
> which can find the host library.
Just passing -lexpat to the cross compiler does not lead the
cross-compiler to look in /usr/lib64. The cross-compiler normally only
looks in its sysroot for libraries.
So there must be some -L/usr/lib64 option that tells the cross-compiler
to look into this folder.
> Unfortunately, the change needs to be in configure.in and AUTORECONF
> fails. I've experimented with creating a patch to configure that does
> what I believe autoreconf should do (adds a copy of the libxml
> pkg-config code adjusted for expat). Does that seem a reasonable fix?
> If so, I'll post it.
Posting the patch would already give us some details on the conclusions
of your analysis. Not sure we will apply it as-is though.
What are the autoreconf issues? Can they be fixed easily?
BTW, do you have a minimal defconfig to reproduce the failure?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-15 8:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-13 Thomas Petazzoni
2017-02-14 13:27 ` [Buildroot] Analysis of build " Thomas Petazzoni
2017-02-14 14:51 ` Peter Korsgaard
2017-02-14 15:10 ` Thomas Petazzoni
2017-02-14 19:21 ` Peter Korsgaard
2017-02-14 20:03 ` Thomas Petazzoni
2017-02-14 20:21 ` Peter Korsgaard
2017-02-14 15:44 ` Philippe Proulx
2017-02-14 16:39 ` Yann E. MORIN
2017-02-14 20:02 ` Thomas Petazzoni
2017-02-14 20:05 ` Yann E. MORIN
2017-02-14 18:02 ` Baruch Siach
2017-02-14 19:37 ` Peter Korsgaard
2017-02-14 22:29 ` Thomas Petazzoni
2017-02-15 7:38 ` Peter Korsgaard
2017-02-15 8:33 ` Thomas Petazzoni
2017-02-15 23:14 ` Arnout Vandecappelle
2017-02-16 8:36 ` Thomas Petazzoni
2017-02-15 2:45 ` Sam Bobroff
2017-02-15 8:37 ` Thomas Petazzoni [this message]
2017-02-15 13:22 ` Gustavo Zacarias
2017-02-16 20:34 ` Bernd Kuhls
2017-02-22 11:26 ` [Buildroot] [arc-buildroot] " Vlad Zakharov
2017-02-22 12:48 ` Thomas Petazzoni
2017-02-22 13:01 ` Vlad Zakharov
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=20170215093723.00b3d499@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