From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Problem building libglib2
Date: Thu, 29 Nov 2012 10:28:11 +0100 [thread overview]
Message-ID: <50B72AAB.2020402@mind.be> (raw)
In-Reply-To: <201211291121.46456.manningc2@actrix.gen.nz>
On 28/11/12 23:21, Charles Manning wrote:
> On Thursday 29 November 2012 10:59:04 Arnout Vandecappelle wrote:
[snip]
>> Could you (and Alex):
>> - tell us which host environment you have;
>> - re-run the failed build with 'V=1 make libglib2' and
>> post the failed command (should be something starting with:
>> /bin/sh ../../libtool --tag=CC --mode=link ...)
>> - post output/build/libglib2-2.30.3/config.log
>> - post output/build/libglib2-2.30.3/gobject/Makefile
>>
>>
>> I vaguely remember having seen this problem before, but can't remember
>> if and how I solved it :-(
>
> Thanks for the help so far...
>
> I get this problem on my main work PC which is running Ubuntu 10.10 x32. It
> works OK on a machine with Ubuntu 10.04 x64.
So the link command ran by libtool is:
/opt/buildroot/buildroot/output/host/usr/bin/arm-none-linux-gnueabi-gcc -shared -fPIC -DPIC
.libs/libgobject_2_0_la-gatomicarray.o .libs/libgobject_2_0_la-gbinding.o .libs/libgobject_2_0_la-gboxed.o
.libs/libgobject_2_0_la-gclosure.o .libs/libgobject_2_0_la-genums.o .libs/libgobject_2_0_la-gmarshal.o
.libs/libgobject_2_0_la-gobject.o .libs/libgobject_2_0_la-gparam.o .libs/libgobject_2_0_la-gparamspecs.o
.libs/libgobject_2_0_la-gsignal.o .libs/libgobject_2_0_la-gsourceclosure.o .libs/libgobject_2_0_la-gtype.o
.libs/libgobject_2_0_la-gtypemodule.o .libs/libgobject_2_0_la-gtypeplugin.o .libs/libgobject_2_0_la-gvalue.o
.libs/libgobject_2_0_la-gvaluearray.o .libs/libgobject_2_0_la-gvaluetransform.o .libs/libgobject_2_0_la-gvaluetypes.o
-Wl,-rpath -Wl,/opt/buildroot/buildroot/output/build/libglib2-2.30.3/glib/.libs -Wl,-rpath
-Wl,/opt/buildroot/buildroot/output/build/libglib2-2.30.3/gthread/.libs
-L/opt/buildroot/buildroot/output/build/libglib2-2.30.3/glib/.libs ../glib/.libs/libglib-2.0.so ../
gthread/.libs/libgthread-2.0.so -lpthread
/opt/buildroot/buildroot/output/build/libglib2-2.30.3/glib/.libs/libglib-2.0.so -lrt
-L/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib -lffi -Os -Wl,-Bsymbolic-functions -Wl,-soname
-Wl,libgobject-2.0.so.0 -Wl,-version-script -Wl,.libs/libgobject-2.0.ver -o .libs/libgobject-2.0.so.0.3000.3
(Just to be sure, could you go to the gobject directory and run the
above command to verify that it fails in the same way? And also add the
-v option to it, so we can see how exactly gcc calls ld.)
There are two strange things with this:
1. There is no mention at all of /lib or /usr/lib so why is ld looking
for pthread in those paths?
2. libtool adds -L/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib
-- where does that come from?
Maybe there's something fishy in your environment. Can you run
env | grep /lib
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-11-29 9:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 1:37 [Buildroot] Problem building libglib2 Charles Manning
2012-11-28 13:31 ` Thomas Petazzoni
2012-11-28 18:09 ` Charles Manning
2012-11-28 21:59 ` Arnout Vandecappelle
[not found] ` <201211291121.46456.manningc2@actrix.gen.nz>
2012-11-29 9:28 ` Arnout Vandecappelle [this message]
2012-11-29 17:52 ` Charles Manning
2012-11-29 18:08 ` Thomas Petazzoni
2012-11-29 18:22 ` Arnout Vandecappelle
2012-11-29 18:31 ` Charles Manning
2012-11-29 20:27 ` Arnout Vandecappelle
2012-11-29 23:11 ` Thomas Petazzoni
2012-11-30 8:37 ` Arnout Vandecappelle
2012-12-02 22:42 ` Charles Manning
2014-08-22 14:13 ` oscarin
2014-08-24 21:04 ` 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=50B72AAB.2020402@mind.be \
--to=arnout@mind.be \
--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