From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Fri, 12 Feb 2010 08:49:31 +0100 Subject: [Buildroot] libglib2 build failure In-Reply-To: <20100210004822.5cc69bd2@surf> References: <20100210004822.5cc69bd2@surf> Message-ID: <20100212084931.789b4393@surf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Wed, 10 Feb 2010 00:48:22 +0100 Thomas Petazzoni 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