[Buildroot] Problem building libglib2

[Buildroot] Problem building libglib2

[Charles Manning]

Hello

I'm a buildroot newbie and am trying to figure out what went wrong here.

make[5]: Entering directory
`/opt/buildroot/buildroot/output/build/libglib2-2.30.3/gobject'
  CCLD   libgobject-2.0.la
/opt/buildroot/buildroot/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.6.3/../../../../arm-none-linux-gnueabi/bin/ld:
skipping incompatible /lib/libpthread.so.0 when searching for
/lib/libpthread.so.0
/opt/buildroot/buildroot/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.6.3/../../../../arm-none-linux-gnueabi/bin/ld:
cannot find /lib/libpthread.so.0
/opt/buildroot/buildroot/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.6.3/../../../../arm-none-linux-gnueabi/bin/ld:
skipping incompatible /usr/lib/libpthread_nonshared.a when searching
for /usr/lib/libpthread_nonshared.a
/opt/buildroot/buildroot/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.6.3/../../../../arm-none-linux-gnueabi/bin/ld:
cannot find /usr/lib/libpthread_nonshared.a
collect2: ld returned 1 exit status
make[5]: *** [libgobject-2.0.la] Error 1
make[5]: Leaving directory
`/opt/buildroot/buildroot/output/build/libglib2-2.30.3/gobject'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
`/opt/buildroot/buildroot/output/build/libglib2-2.30.3/gobject'
make[3]: *** [all] Error 2
make[3]: Leaving directory
`/opt/buildroot/buildroot/output/build/libglib2-2.30.3/gobject'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/opt/buildroot/buildroot/output/build/libglib2-2.30.3'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/opt/buildroot/buildroot/output/build/libglib2-2.30.3'
make: *** [/opt/buildroot/buildroot/output/build/libglib2-2.30.3/.stamp_built]
Error 2


As far as I can tell, this failed building libglib because various
files were missing. For example  /lib/libpthread.so.0.

However if I look in staging, that file exists:

charles at charles-laptop:/opt/buildroot/buildroot$ ls -al
output/staging/lib/libp*
-rwxr-xr-x 1 charles charles  19467 2012-05-29 00:41
output/staging/lib/libpcprofile.so
-rwxr-xr-x 1 charles charles 144489 2012-05-29 00:41
output/staging/lib/libpthread-2.15.so
lrwxrwxrwx 1 charles charles     18 2012-11-28 12:03
output/staging/lib/libpthread.so.0 -> libpthread-2.15.so
charles at charles-laptop:/opt/buildroot/buildroot$

So... please help the newbie....

Thanks

Charles

[Buildroot] Problem building libglib2

[Thomas Petazzoni]

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?

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Problem building libglib2

[Charles Manning]

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

btw: Thank you very much for all you do for the community.

Regards

Charles
-------------- next part --------------
A non-text attachment was scrubbed...
Name: failing-config
Type: application/octet-stream
Size: 25149 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121129/37202728/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config-201211281330
Type: application/octet-stream
Size: 25038 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121129/37202728/attachment-0003.obj>

[Buildroot] Problem building libglib2

[Arnout Vandecappelle]

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

[Buildroot] Problem building libglib2

[Arnout Vandecappelle]

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

[Buildroot] Problem building libglib2

[Charles Manning]

On Thursday 29 November 2012 22:28:11 Arnout Vandecappelle wrote:
> 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

Aaaarrrrggghhhh!!!!

I have this system set up to automatically set up for openembedded.
 That defines PKG_CONFIG_PATH and adds some stuff to PATH which is probably 
messing things up.

I turned off the openembedded auto configuration, nuked output/ and make ran 
to completion.

I have now also learned a lot more about digging around in buildroot.

Thanks. 

Charles

[Buildroot] Problem building libglib2

[Thomas Petazzoni]

Dear Charles Manning,

On Fri, 30 Nov 2012 06:52:44 +1300, Charles Manning wrote:
> >   Maybe there's something fishy in your environment.  Can you run
> > env | grep /lib
> 
> Aaaarrrrggghhhh!!!!
> 
> I have this system set up to automatically set up for openembedded.
>  That defines PKG_CONFIG_PATH and adds some stuff to PATH which is probably 
> messing things up.
> 
> I turned off the openembedded auto configuration, nuked output/ and make ran 
> to completion.
> 
> I have now also learned a lot more about digging around in buildroot.

Wait, wait, could you please reproduce the problem, and reply to
Arnout's questions (sending us the output of env | grep /lib, or even
the entire output of env if it doesn't contain any sensitive
information).

I would like to this which environment variable was causing the
problem, and if we can add a check in Buildroot for this environment
variable, in order to avoid similar issues in the future.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Problem building libglib2

[Arnout Vandecappelle]

On 29/11/12 19:08, Thomas Petazzoni wrote:
> Dear Charles Manning,
>
> On Fri, 30 Nov 2012 06:52:44 +1300, Charles Manning wrote:
>>>    Maybe there's something fishy in your environment.  Can you run
>>> env | grep /lib
>>
>> Aaaarrrrggghhhh!!!!
>>
>> I have this system set up to automatically set up for openembedded.
>>   That defines PKG_CONFIG_PATH and adds some stuff to PATH which is probably
>> messing things up.
>>
>> I turned off the openembedded auto configuration, nuked output/ and make ran
>> to completion.
>>
>> I have now also learned a lot more about digging around in buildroot.
>
> Wait, wait, could you please reproduce the problem, and reply to
> Arnout's questions (sending us the output of env | grep /lib, or even
> the entire output of env if it doesn't contain any sensitive
> information).
>
> I would like to this which environment variable was causing the
> problem, and if we can add a check in Buildroot for this environment
> variable, in order to avoid similar issues in the future.

  After a second look in config.log:

pkg_cv_DBUS1_CFLAGS='-I/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/include/dbus-1.0 
-I/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib/dbus-1.0/include  '
pkg_cv_DBUS1_LIBS='-L/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib -ldbus-1 -lpthread -lrt  '
pkg_cv_LIBFFI_CFLAGS=' '
pkg_cv_LIBFFI_LIBS='-L/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib -lffi  '
pkg_cv_ZLIB_CFLAGS='-I/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/include  '
pkg_cv_ZLIB_LIBS='-L/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib -lz  '


  I really don't see how this can happen: we unexport PKG_CONFIG_PATH and set
PKG_CONFIG explicitly in the Makefile...

  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

[Buildroot] Problem building libglib2

[Charles Manning]

On Friday 30 November 2012 07:08:13 Thomas Petazzoni wrote:
> Dear Charles Manning,
>
> On Fri, 30 Nov 2012 06:52:44 +1300, Charles Manning wrote:
> > >   Maybe there's something fishy in your environment.  Can you run
> > > env | grep /lib
> >
> > Aaaarrrrggghhhh!!!!
> >
> > I have this system set up to automatically set up for openembedded.
> >  That defines PKG_CONFIG_PATH and adds some stuff to PATH which is
> > probably messing things up.
> >
> > I turned off the openembedded auto configuration, nuked output/ and make
> > ran to completion.
> >
> > I have now also learned a lot more about digging around in buildroot.
>
> Wait, wait, could you please reproduce the problem, and reply to
> Arnout's questions (sending us the output of env | grep /lib, or even
> the entire output of env if it doesn't contain any sensitive
> information).
>
> I would like to this which environment variable was causing the
> problem, and if we can add a check in Buildroot for this environment
> variable, in order to avoid similar issues in the future.
>

The problem was cause by running the openembedded toolchain env setup script 
shown below and attached incase it gets too badly messed up by mail.

export PATH=/usr/local/angstrom/arm/bin:$PATH
export LIBTOOL_SYSROOT_PATH=/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi
export 
PKG_CONFIG_SYSROOT_DIR=/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi
export 
PKG_CONFIG_PATH=/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib/pkgconfig
export QTDIR=/usr/local/angstrom/arm
export CONFIG_SITE=/usr/local/angstrom/arm/site-config
alias 
opkg='LD_LIBRARY_PATH=/usr/local/angstrom/arm/lib /usr/local/angstrom/arm/bin/opkg-cl -f /usr/local/angstrom/arm/etc/opkg-sdk.conf -o /usr/local/angstrom/arm'
alias 
opkg-target='LD_LIBRARY_PATH=/usr/local/angstrom/arm/lib /usr/local/angstrom/arm/bin/opkg-cl -f /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/etc/opkg.conf -o /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi'


I had added the following line to bashrc:

. /path/environment-setup

that caused it to always be added.

I see the Makefile has a line
 unexport PKG_CONFIG_PATH
perhaps that should be
 unset PKG_CONFIG_PATH


Is that enough info?

Sorry I have to go to the day job now, so if you want more I will have to work 
on that later.


Thanks for your efforts!

-- CHarles
-------------- next part --------------
export PATH=/usr/local/angstrom/arm/bin:$PATH
export LIBTOOL_SYSROOT_PATH=/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi
export PKG_CONFIG_SYSROOT_DIR=/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi
export PKG_CONFIG_PATH=/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib/pkgconfig
export QTDIR=/usr/local/angstrom/arm
export CONFIG_SITE=/usr/local/angstrom/arm/site-config
alias opkg='LD_LIBRARY_PATH=/usr/local/angstrom/arm/lib /usr/local/angstrom/arm/bin/opkg-cl -f /usr/local/angstrom/arm/etc/opkg-sdk.conf -o /usr/local/angstrom/arm'
alias opkg-target='LD_LIBRARY_PATH=/usr/local/angstrom/arm/lib /usr/local/angstrom/arm/bin/opkg-cl -f /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/etc/opkg.conf -o /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi'

[Buildroot] Problem building libglib2

[Arnout Vandecappelle]

On 29/11/12 19:31, Charles Manning wrote:
> export
> PKG_CONFIG_SYSROOT_DIR=/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi

  That's the one.

  Charles, could you verify by setting this variable and rebuilding libglib2:

PKG_CONFIG_SYSROOT_DIR=/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi \
     make libglib2-dirclean libglib2


  All,

  We could obviously solve this by unexporting PKG_CONFIG_SYSROOT_DIR, but
perhaps the better approach is to remove those environment variables from our
custom pkgconf?

  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

[Buildroot] Problem building libglib2

[Thomas Petazzoni]

Dear Arnout Vandecappelle,

On Thu, 29 Nov 2012 21:27:56 +0100, Arnout Vandecappelle wrote:

>   We could obviously solve this by unexporting PKG_CONFIG_SYSROOT_DIR, but
> perhaps the better approach is to remove those environment variables from our
> custom pkgconf?

No, we use PKG_CONFIG_SYSROOT_DIR="/" when we build packages for the
host, so we can't simply remove support for the PKG_CONFIG_SYSROOT_DIR
environment variable. Unexporting PKG_CONFIG_SYSROOT_DIR sounds like
the good solution here.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Problem building libglib2

[Arnout Vandecappelle]

On 30/11/12 00:11, Thomas Petazzoni wrote:
> Dear Arnout Vandecappelle,
>
> On Thu, 29 Nov 2012 21:27:56 +0100, Arnout Vandecappelle wrote:
>
>>    We could obviously solve this by unexporting PKG_CONFIG_SYSROOT_DIR, but
>> perhaps the better approach is to remove those environment variables from our
>> custom pkgconf?
>
> No, we use PKG_CONFIG_SYSROOT_DIR="/" when we build packages for the
> host, so we can't simply remove support for the PKG_CONFIG_SYSROOT_DIR
> environment variable. Unexporting PKG_CONFIG_SYSROOT_DIR sounds like
> the good solution here.

  Right.

  Charles, would you care to prepare a patch that unexports PKG_CONFIG_SYSROOT_DIR
and test it in your angstrom environment?

  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

[Buildroot] Problem building libglib2

[Charles Manning]

On Friday 30 November 2012 21:37:07 Arnout Vandecappelle wrote:
> On 30/11/12 00:11, Thomas Petazzoni wrote:
> > Dear Arnout Vandecappelle,
> >
> > On Thu, 29 Nov 2012 21:27:56 +0100, Arnout Vandecappelle wrote:
> >>    We could obviously solve this by unexporting PKG_CONFIG_SYSROOT_DIR,
> >> but perhaps the better approach is to remove those environment variables
> >> from our custom pkgconf?
> >
> > No, we use PKG_CONFIG_SYSROOT_DIR="/" when we build packages for the
> > host, so we can't simply remove support for the PKG_CONFIG_SYSROOT_DIR
> > environment variable. Unexporting PKG_CONFIG_SYSROOT_DIR sounds like
> > the good solution here.
>
>   Right.
>
>   Charles, would you care to prepare a patch that unexports
> PKG_CONFIG_SYSROOT_DIR and test it in your angstrom environment?

This works and I have submitted a patch.

Thanks

-- Charles

[Buildroot] Problem building libglib2

[oscarin]

Hello,

I'm having kind of the same problem when building my system. When i tried to
build "directfb-examples 1.6.0 Building" in "buildroot-2013.08.1" i have
this messages: 

/home/oscarin/Downloads/felabs/sysdev/buildroot/buildroot-2013.08.1/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.6.1/../../../../arm-none-linux-gnueabi/bin/ld:
cannot find /lib/libpthread.so.0
/home/oscarin/Downloads/felabs/sysdev/buildroot/buildroot-2013.08.1/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.6.1/../../../../arm-none-linux-gnueabi/bin/ld:
cannot find /usr/lib/libpthread_nonshared.a
collect2: ld returned 1 exit status
make[3]: *** [df_knuckles] Error 1
make[3]: Leaving directory
`/home/oscarin/Downloads/felabs/sysdev/buildroot/buildroot-2013.08.1/output/build/directfb-examples-1.6.0/src/df_knuckles'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/oscarin/Downloads/felabs/sysdev/buildroot/buildroot-2013.08.1/output/build/directfb-examples-1.6.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/oscarin/Downloads/felabs/sysdev/buildroot/buildroot-2013.08.1/output/build/directfb-examples-1.6.0'
make: ***
[/home/oscarin/Downloads/felabs/sysdev/buildroot/buildroot-2013.08.1/output/build/directfb-examples-1.6.0/.stamp_built]
Error 2

Would you please help me ?




--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Problem-building-libglib2-tp35486p77917.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

[Buildroot] Problem building libglib2

[Thomas Petazzoni]

Dear oscarin,

On Fri, 22 Aug 2014 07:13:36 -0700 (PDT), oscarin wrote:
> I'm having kind of the same problem when building my system. When i tried to
> build "directfb-examples 1.6.0 Building" in "buildroot-2013.08.1" i have
> this messages: 
> 
> /home/oscarin/Downloads/felabs/sysdev/buildroot/buildroot-2013.08.1/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.6.1/../../../../arm-none-linux-gnueabi/bin/ld:
> cannot find /lib/libpthread.so.0
> /home/oscarin/Downloads/felabs/sysdev/buildroot/buildroot-2013.08.1/output/host/opt/ext-toolchain/bin/../lib/gcc/arm-none-linux-gnueabi/4.6.1/../../../../arm-none-linux-gnueabi/bin/ld:
> cannot find /usr/lib/libpthread_nonshared.a
> collect2: ld returned 1 exit status
> make[3]: *** [df_knuckles] Error 1
> make[3]: Leaving directory
> `/home/oscarin/Downloads/felabs/sysdev/buildroot/buildroot-2013.08.1/output/build/directfb-examples-1.6.0/src/df_knuckles'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory
> `/home/oscarin/Downloads/felabs/sysdev/buildroot/buildroot-2013.08.1/output/build/directfb-examples-1.6.0/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/home/oscarin/Downloads/felabs/sysdev/buildroot/buildroot-2013.08.1/output/build/directfb-examples-1.6.0'
> make: ***
> [/home/oscarin/Downloads/felabs/sysdev/buildroot/buildroot-2013.08.1/output/build/directfb-examples-1.6.0/.stamp_built]
> Error 2
> 
> Would you please help me ?

Thanks for your report. Instead of using a 2 years old thread, it would
have been better to post this as a new message to the mailing list.

Could you retry with the latest Buildroot version (2014.05), and if the
problem still exists, please include your complete Buildroot .config
file so that we can reproduce the issue.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com