From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] libglib2 build failure
Date: Fri, 12 Feb 2010 08:49:31 +0100 [thread overview]
Message-ID: <20100212084931.789b4393@surf> (raw)
In-Reply-To: <20100210004822.5cc69bd2@surf>
On Wed, 10 Feb 2010 00:48:22 +0100
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> While trying to compile libglib2, I get the following build failure.
> It is the infamous libtool problem, but libglib2 uses libtool 2.x, for
> which our buildroot-libtool.patch does not apply. It happens in an
> external toolchain configuration, and libglib2.0-dev is installed on
> the host.
I've digged into this a bit further. In order to make cleaner tests,
I've created a Debian stable chroot with the minimum set of packages
needed to get Buildroot running
(http://free-electrons.com/~thomas/buildroot/pkg-list). And then I tried
to compile two configurations :
* An ARM configuration, with an internal toolchain (generated by
Buildroot), with Busybox and libglib2. Compiles perfectly.
Config
http://free-electrons.com/~thomas/buildroot/config-internal
Build log
http://free-electrons.com/~thomas/buildroot/build-internal.log
* An ARM configuration, with a CodeSourcery toolchain as an external
toolchain, with Busybox and libglib2. Fails to build libglib2
because it tries to link against /usr/lib/libdl.so.
Config
http://free-electrons.com/~thomas/buildroot/config-ext
Build log
http://free-electrons.com/~thomas/buildroot/build-external.log
So obviously it looks like that the parameter that makes it fail is the
external toolchain. Any idea on what impact it could have on libtool ?
Thanks for your input and ideas,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-02-12 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 23:48 [Buildroot] libglib2 build failure Thomas Petazzoni
2010-02-10 6:26 ` Lionel Landwerlin
2010-02-10 7:26 ` Thomas Petazzoni
2010-02-10 7:51 ` Thomas Petazzoni
2010-02-10 10:06 ` Lionel Landwerlin
2010-02-11 7:44 ` Thomas Petazzoni
2010-02-10 9:56 ` Lionel Landwerlin
2010-02-12 7:49 ` Thomas Petazzoni [this message]
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=20100212084931.789b4393@surf \
--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 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.