From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Problem building libglib2
Date: Wed, 28 Nov 2012 22:59:04 +0100 [thread overview]
Message-ID: <50B68928.4010500@mind.be> (raw)
In-Reply-To: <CAE21AQqs92x6=x_ELTWz7MqMLNDrq9VDXK17+P_2sB-7wc=JXw@mail.gmail.com>
On 28/11/12 19:09, Charles Manning wrote:
> On Thu, Nov 29, 2012 at 2:31 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Dear Charles Manning,
>>
>> On Wed, 28 Nov 2012 14:37:46 +1300, Charles Manning wrote:
>>
>>> I'm a buildroot newbie and am trying to figure out what went wrong
>>> here.
>>
>> This looks odd. Could you give us your Buildroot .config and tell us
>> the Buildroot version you're using?
>
> Hello Thomas
>
> I have been working up from beaglebone defconfig towards a rootfs that
> I want for a project.
>
> The confg-201211281330 worked fine. I then added the bluez package and
> things fell over.
>
> I am using HEAD as of some time yesterday: commit
> 3bdbe9abb90de0262832d5d545f239fa41fb0e91
There was a similar report from Alex (in CC). I tried to reproduce it but
failed. I'll also try with this config.
What is going wrong in your (and Alex's) build is that ld tries to find
libpthread.so.0 in /lib instead of in $(STAGING_DIR)/lib.
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 :-(
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-28 21:59 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 [this message]
[not found] ` <201211291121.46456.manningc2@actrix.gen.nz>
2012-11-29 9:28 ` Arnout Vandecappelle
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=50B68928.4010500@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 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.