[Buildroot] libglib2 (or maybe libffi) build failure

[Buildroot] libglib2 (or maybe libffi) build failure

[Mark Jackson]

Using the latest git top-of-tree, libglib2 fails to compile as follows:-

$ git pull
Already up-to-date.
$ make
...
>>> libffi 3.0.13 Extracting
...
>>> libffi 3.0.13 Patching
...
>>> libffi 3.0.13 Updating config.sub and config.guess
...
>>> libffi 3.0.13 Patching libtool
>>> libffi 3.0.13 Autoreconfiguring
...
>>> libffi 3.0.13 Configuring
...
>>> libffi 3.0.13 Building
...
>>> libffi 3.0.13 Installing to staging directory
...
>>> libffi 3.0.13 Installing to target
...
>>> libglib2 2.36.3 Autoreconfiguring
...
>>> libglib2 2.36.3 Configuring
...
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for LIBFFI... no
configure: error: Package requirements (libffi >= 3.0.0) were not met:

Package libffi was not found in the pkg-config search path.
Perhaps you should add the directory containing `libffi.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libffi' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables LIBFFI_CFLAGS
and LIBFFI_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
make: *** [/home/mpfj/buildroot-bt/output/build/libglib2-2.36.3/.stamp_configured] Error 1
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for LIBFFI... no
configure: error: Package requirements (libffi >= 3.0.0) were not met:

Package libffi was not found in the pkg-config search path.
Perhaps you should add the directory containing `libffi.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libffi' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables LIBFFI_CFLAGS
and LIBFFI_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
make: *** [/home/mpfj/buildroot-bt/output/build/libglib2-2.36.3/.stamp_configured] Error 1

Any clues ?

Below is my "defconfig" as created by 'make savedefconfig'.

Cheers
Mark J.
---
BR2_arm=y
BR2_cortex_a8=y
BR2_JLEVEL=8
BR2_TOOLCHAIN_BUILDROOT_INET_IPV6=y
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_PTHREADS=y
# BR2_UCLIBC_INSTALL_UTILS is not set
BR2_BINUTILS_VERSION_2_23_2=y
BR2_GCC_VERSION_4_8_X=y
BR2_EXTRA_GCC_CONFIG_OPTIONS="--with-fpu=vfpv3 --with-float=hard"
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_TARGET_GENERIC_HOSTNAME="nanobone"
BR2_TARGET_GENERIC_ROOT_PASSWD="rmfMPVaGP3nnjWUV"
BR2_TARGET_GENERIC_GETTY_PORT="ttyO0"
BR2_ROOTFS_OVERLAY="board/newflow/nanobone/skeleton"
BR2_PACKAGE_BUSYBOX_CONFIG="board/newflow/nanobone/busybox-1.21.x.config"
BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y
BR2_PACKAGE_MTD=y
BR2_PACKAGE_I2C_TOOLS=y
BR2_PACKAGE_OPENSSL=y
BR2_PACKAGE_OPENSSL_BIN=y
BR2_PACKAGE_LIBESMTP=y
BR2_PACKAGE_LIBFCGI=y
BR2_PACKAGE_AVAHI=y
BR2_PACKAGE_BLUEZ_UTILS=y
BR2_PACKAGE_BLUEZ_UTILS_COMPAT=y
BR2_PACKAGE_DROPBEAR=y
BR2_PACKAGE_DROPBEAR_DISABLE_REVERSEDNS=y
BR2_PACKAGE_IW=y
BR2_PACKAGE_LIGHTTPD=y
BR2_PACKAGE_NTP=y
BR2_PACKAGE_NTP_SNTP=y
# BR2_PACKAGE_NTP_NTPD is not set
BR2_PACKAGE_WIRELESS_TOOLS=y
BR2_PACKAGE_WPA_SUPPLICANT=y
BR2_TARGET_ROOTFS_UBIFS=y
BR2_TARGET_ROOTFS_UBIFS_LEBSIZE=0x1ff80
BR2_TARGET_ROOTFS_UBIFS_MINIOSIZE=0x1
BR2_TARGET_ROOTFS_UBIFS_MAXLEBCNT=464
BR2_TARGET_ROOTFS_UBIFS_RT_NONE=y
BR2_TARGET_ROOTFS_UBI=y
BR2_TARGET_ROOTFS_UBI_SUBSIZE=1
BR2_PACKAGE_HOST_UBOOT_TOOLS=y

[Buildroot] libglib2 (or maybe libffi) build failure

[Thomas Petazzoni]

Dear Mark Jackson,

On Wed, 27 Nov 2013 15:28:12 +0000, Mark Jackson wrote:
> Using the latest git top-of-tree, libglib2 fails to compile as follows:-
> 
> $ git pull
> Already up-to-date.
> $ make

[...]

> Alternatively, you may set the environment variables LIBFFI_CFLAGS
> and LIBFFI_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> make: *** [/home/mpfj/buildroot-bt/output/build/libglib2-2.36.3/.stamp_configured] Error 1
> 
> Any clues ?

Interesting, thanks. Can you see in output/staging/usr/lib/pkgconfig/
if you have the file named libffi.pc ?

If that's the case, then, can you try:

	./output/host/usr/bin/pkg-config --list-all

and see if libffi is part of the list ?

If that's the case, can you pastebin (http://code.bulix.org) the entire
output/build/libglib2-2.36.3/config.log file, and give us the URL at
which it was posted?

Finally, can you inspect your environment (by running "env") to see if
there's anything suspicious. Ideally, giving your environment might be
useful, but read it first to remove any personal stuff from it, if
applicable.

> BR2_TARGET_GENERIC_ROOT_PASSWD="rmfMPVaGP3nnjWUV"

Hopefully it's not an important password :)

Best regards,

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

[Buildroot] libglib2 (or maybe libffi) build failure

[Mark Jackson]

On 27/11/13 16:15, Thomas Petazzoni wrote:
> Dear Mark Jackson,
> 
> On Wed, 27 Nov 2013 15:28:12 +0000, Mark Jackson wrote:
>> Using the latest git top-of-tree, libglib2 fails to compile as follows:-
>>
>> $ git pull
>> Already up-to-date.
>> $ make
> 
> [...]
> 
>> Alternatively, you may set the environment variables LIBFFI_CFLAGS
>> and LIBFFI_LIBS to avoid the need to call pkg-config.
>> See the pkg-config man page for more details.
>> make: *** [/home/mpfj/buildroot-bt/output/build/libglib2-2.36.3/.stamp_configured] Error 1
>>
>> Any clues ?
> 
> Interesting, thanks. Can you see in output/staging/usr/lib/pkgconfig/
> if you have the file named libffi.pc ?

Yes ...

$ ls output/staging/usr/lib/pkgconfig/ -la
total 64
drwxrwxr-x 2 mpfj mpfj 4096 Nov 27 15:14 .
drwxrwxr-x 9 mpfj mpfj 4096 Nov 27 15:14 ..
-rw-r--r-- 1 mpfj mpfj  258 Nov  6 12:35 avahi-core.pc
-rw-r--r-- 1 mpfj mpfj  508 Nov 27 10:06 dbus-1.pc
-rw-r--r-- 1 mpfj mpfj  221 Nov 25 12:06 expat.pc
-rw-r--r-- 1 mpfj mpfj  255 Nov  6 12:36 libcrypto.pc
-rw-r--r-- 1 mpfj mpfj  260 Nov  6 12:35 libdaemon.pc
-rw-r--r-- 1 mpfj mpfj  169 Nov 27 15:14 libffi.pc
-rw-r--r-- 1 mpfj mpfj  222 Nov  6 12:36 libnl-3.0.pc
-rw-r--r-- 1 mpfj mpfj  298 Nov  6 12:36 libnl-cli-3.0.pc
-rw-r--r-- 1 mpfj mpfj  236 Nov  6 12:36 libnl-genl-3.0.pc
-rw-r--r-- 1 mpfj mpfj  240 Nov  6 12:36 libnl-nf-3.0.pc
-rw-r--r-- 1 mpfj mpfj  245 Nov  6 12:36 libnl-route-3.0.pc
-rw-r--r-- 1 mpfj mpfj  270 Nov  6 12:36 libssl.pc
-rw-r--r-- 1 mpfj mpfj  280 Nov  6 12:36 openssl.pc
-rw-r--r-- 1 mpfj mpfj  252 Nov 27 10:08 zlib.pc

> If that's the case, then, can you try:
> 
> 	./output/host/usr/bin/pkg-config --list-all
> 
> and see if libffi is part of the list ?

No ...

$ ./output/host/usr/bin/pkg-config --list-all 
libnl-route-3.0                libnl-route - Netlink Routing Family Library
avahi-core                     avahi-core - Avahi Multicast DNS Responder (Embeddable Stack)
zlib                           zlib - zlib compression library
libssl                         OpenSSL - Secure Sockets Layer and cryptography libraries
libnl-3.0                      libnl - Convenience library for netlink sockets
libnl-genl-3.0                 libnl-genl - Generic Netlink Library
libnl-nf-3.0                   libnl-nf - Netfilter Netlink Library
libnl-cli-3.0                  libnl-cli - Command Line Interface library for netlink sockets
libcrypto                      OpenSSL-libcrypto - OpenSSL cryptography library
openssl                        OpenSSL - Secure Sockets Layer and cryptography libraries and tools
libdaemon                      libdaemon - a lightweight C library that eases the writing of UNIX daemons

> If that's the case, can you pastebin (http://code.bulix.org) the entire
> output/build/libglib2-2.36.3/config.log file, and give us the URL at
> which it was posted?

http://code.bulix.org/aq3veb-85084

> Finally, can you inspect your environment (by running "env") to see if
> there's anything suspicious. Ideally, giving your environment might be
> useful, but read it first to remove any personal stuff from it, if
> applicable.

http://code.bulix.org/ng3wku-85083

>> BR2_TARGET_GENERIC_ROOT_PASSWD="rmfMPVaGP3nnjWUV"
> 
> Hopefully it's not an important password :)

Ho, ho ... nope !!

Cheers
Mark J.

[Buildroot] libglib2 (or maybe libffi) build failure

[Thomas Petazzoni]

Dear Mark Jackson,

On Wed, 27 Nov 2013 16:25:59 +0000, Mark Jackson wrote:

> > Interesting, thanks. Can you see in output/staging/usr/lib/pkgconfig/
> > if you have the file named libffi.pc ?
> 
> Yes ...
> 
> $ ls output/staging/usr/lib/pkgconfig/ -la
> total 64
> drwxrwxr-x 2 mpfj mpfj 4096 Nov 27 15:14 .
> drwxrwxr-x 9 mpfj mpfj 4096 Nov 27 15:14 ..
> -rw-r--r-- 1 mpfj mpfj  258 Nov  6 12:35 avahi-core.pc
> -rw-r--r-- 1 mpfj mpfj  508 Nov 27 10:06 dbus-1.pc
> -rw-r--r-- 1 mpfj mpfj  221 Nov 25 12:06 expat.pc
> -rw-r--r-- 1 mpfj mpfj  255 Nov  6 12:36 libcrypto.pc
> -rw-r--r-- 1 mpfj mpfj  260 Nov  6 12:35 libdaemon.pc
> -rw-r--r-- 1 mpfj mpfj  169 Nov 27 15:14 libffi.pc
> -rw-r--r-- 1 mpfj mpfj  222 Nov  6 12:36 libnl-3.0.pc
> -rw-r--r-- 1 mpfj mpfj  298 Nov  6 12:36 libnl-cli-3.0.pc
> -rw-r--r-- 1 mpfj mpfj  236 Nov  6 12:36 libnl-genl-3.0.pc
> -rw-r--r-- 1 mpfj mpfj  240 Nov  6 12:36 libnl-nf-3.0.pc
> -rw-r--r-- 1 mpfj mpfj  245 Nov  6 12:36 libnl-route-3.0.pc
> -rw-r--r-- 1 mpfj mpfj  270 Nov  6 12:36 libssl.pc
> -rw-r--r-- 1 mpfj mpfj  280 Nov  6 12:36 openssl.pc
> -rw-r--r-- 1 mpfj mpfj  252 Nov 27 10:08 zlib.pc

Ok. What does libffi.pc contains?

> > If that's the case, then, can you try:
> > 
> > 	./output/host/usr/bin/pkg-config --list-all
> > 
> > and see if libffi is part of the list ?
> 
> No ...
> 
> $ ./output/host/usr/bin/pkg-config --list-all 
> libnl-route-3.0                libnl-route - Netlink Routing Family Library
> avahi-core                     avahi-core - Avahi Multicast DNS Responder (Embeddable Stack)
> zlib                           zlib - zlib compression library
> libssl                         OpenSSL - Secure Sockets Layer and cryptography libraries
> libnl-3.0                      libnl - Convenience library for netlink sockets
> libnl-genl-3.0                 libnl-genl - Generic Netlink Library
> libnl-nf-3.0                   libnl-nf - Netfilter Netlink Library
> libnl-cli-3.0                  libnl-cli - Command Line Interface library for netlink sockets
> libcrypto                      OpenSSL-libcrypto - OpenSSL cryptography library
> openssl                        OpenSSL - Secure Sockets Layer and cryptography libraries and tools
> libdaemon                      libdaemon - a lightweight C library that eases the writing of UNIX daemons

Weird, that matches more or less the contents of the usr/lib/pkgconfig
directory above, with the exception of dbus-1, expat, libcrypto and
libffi.

> > If that's the case, can you pastebin (http://code.bulix.org) the entire
> > output/build/libglib2-2.36.3/config.log file, and give us the URL at
> > which it was posted?
> 
> http://code.bulix.org/aq3veb-85084

Ok. Nothing interesting here.

> > Finally, can you inspect your environment (by running "env") to see if
> > there's anything suspicious. Ideally, giving your environment might be
> > useful, but read it first to remove any personal stuff from it, if
> > applicable.
> 
> http://code.bulix.org/ng3wku-85083

However here, I see:

PATH=/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/mpfj/buildroot/output/host/usr/bin

So you have /home/mpfj/buildroot/output/host/usr/bin but the failing
build takes place in /home/mpjf/buildroot-bt/.

Can you remove /home/mpfj/buildroot/output/host/usr/bin from your PATH
and try again?

To be honest, I don't quite see why this would be causing problems, but
that's the only possibly "odd" thing that I see in your
configuration/setup for the moment.

Thanks!

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

[Buildroot] libglib2 (or maybe libffi) build failure

[Mark Jackson]

On 27/11/13 16:37, Thomas Petazzoni wrote:
> Dear Mark Jackson,
> 
> On Wed, 27 Nov 2013 16:25:59 +0000, Mark Jackson wrote:
> 
>>> Interesting, thanks. Can you see in output/staging/usr/lib/pkgconfig/
>>> if you have the file named libffi.pc ?
>>
>> Yes ...
>>
>> $ ls output/staging/usr/lib/pkgconfig/ -la
>> total 64
>> drwxrwxr-x 2 mpfj mpfj 4096 Nov 27 15:14 .
>> drwxrwxr-x 9 mpfj mpfj 4096 Nov 27 15:14 ..
>> -rw-r--r-- 1 mpfj mpfj  258 Nov  6 12:35 avahi-core.pc
>> -rw-r--r-- 1 mpfj mpfj  508 Nov 27 10:06 dbus-1.pc
>> -rw-r--r-- 1 mpfj mpfj  221 Nov 25 12:06 expat.pc
>> -rw-r--r-- 1 mpfj mpfj  255 Nov  6 12:36 libcrypto.pc
>> -rw-r--r-- 1 mpfj mpfj  260 Nov  6 12:35 libdaemon.pc
>> -rw-r--r-- 1 mpfj mpfj  169 Nov 27 15:14 libffi.pc
>> -rw-r--r-- 1 mpfj mpfj  222 Nov  6 12:36 libnl-3.0.pc
>> -rw-r--r-- 1 mpfj mpfj  298 Nov  6 12:36 libnl-cli-3.0.pc
>> -rw-r--r-- 1 mpfj mpfj  236 Nov  6 12:36 libnl-genl-3.0.pc
>> -rw-r--r-- 1 mpfj mpfj  240 Nov  6 12:36 libnl-nf-3.0.pc
>> -rw-r--r-- 1 mpfj mpfj  245 Nov  6 12:36 libnl-route-3.0.pc
>> -rw-r--r-- 1 mpfj mpfj  270 Nov  6 12:36 libssl.pc
>> -rw-r--r-- 1 mpfj mpfj  280 Nov  6 12:36 openssl.pc
>> -rw-r--r-- 1 mpfj mpfj  252 Nov 27 10:08 zlib.pc
> 
> Ok. What does libffi.pc contains?

$ cat output/staging/usr/lib/pkgconfig/libffi.pc 
prefix=/usr
exec_prefix=/usr
libdir=${exec_prefix}/lib

Name: libffi
Description: Library supporting Foreign Function Interfaces
Version: 3.0.13
Libs: -L${libdir} -lffi

>>> If that's the case, then, can you try:
>>>
>>> 	./output/host/usr/bin/pkg-config --list-all
>>>
>>> and see if libffi is part of the list ?
>>
>> No ...
>>
>> $ ./output/host/usr/bin/pkg-config --list-all 
>> libnl-route-3.0                libnl-route - Netlink Routing Family Library
>> avahi-core                     avahi-core - Avahi Multicast DNS Responder (Embeddable Stack)
>> zlib                           zlib - zlib compression library
>> libssl                         OpenSSL - Secure Sockets Layer and cryptography libraries
>> libnl-3.0                      libnl - Convenience library for netlink sockets
>> libnl-genl-3.0                 libnl-genl - Generic Netlink Library
>> libnl-nf-3.0                   libnl-nf - Netfilter Netlink Library
>> libnl-cli-3.0                  libnl-cli - Command Line Interface library for netlink sockets
>> libcrypto                      OpenSSL-libcrypto - OpenSSL cryptography library
>> openssl                        OpenSSL - Secure Sockets Layer and cryptography libraries and tools
>> libdaemon                      libdaemon - a lightweight C library that eases the writing of UNIX daemons
> 
> Weird, that matches more or less the contents of the usr/lib/pkgconfig
> directory above, with the exception of dbus-1, expat, libcrypto and
> libffi.
> 
>>> If that's the case, can you pastebin (http://code.bulix.org) the entire
>>> output/build/libglib2-2.36.3/config.log file, and give us the URL at
>>> which it was posted?
>>
>> http://code.bulix.org/aq3veb-85084
> 
> Ok. Nothing interesting here.
> 
>>> Finally, can you inspect your environment (by running "env") to see if
>>> there's anything suspicious. Ideally, giving your environment might be
>>> useful, but read it first to remove any personal stuff from it, if
>>> applicable.
>>
>> http://code.bulix.org/ng3wku-85083
> 
> However here, I see:
> 
> PATH=/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/mpfj/buildroot/output/host/usr/bin
> 
> So you have /home/mpfj/buildroot/output/host/usr/bin but the failing
> build takes place in /home/mpjf/buildroot-bt/.
> 
> Can you remove /home/mpfj/buildroot/output/host/usr/bin from your PATH
> and try again?
> 
> To be honest, I don't quite see why this would be causing problems, but
> that's the only possibly "odd" thing that I see in your
> configuration/setup for the moment.

Still fails ...

$ echo $PATH
/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
$ make
>>> libglib2 2.36.3 Autoreconfiguring
...
>>> libglib2 2.36.3 Configuring
...
checking for stdint.h... yes
checking for unistd.h... yes
checking for LIBFFI... no
configure: error: Package requirements (libffi >= 3.0.0) were not met:

Package libffi was not found in the pkg-config search path.
Perhaps you should add the directory containing `libffi.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libffi' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables LIBFFI_CFLAGS
and LIBFFI_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

[Buildroot] libglib2 (or maybe libffi) build failure

[Thomas Petazzoni]

Dear Mark Jackson,

On Wed, 27 Nov 2013 16:45:36 +0000, Mark Jackson wrote:

> > Ok. What does libffi.pc contains?
> 
> $ cat output/staging/usr/lib/pkgconfig/libffi.pc 
> prefix=/usr
> exec_prefix=/usr
> libdir=${exec_prefix}/lib
> 
> Name: libffi
> Description: Library supporting Foreign Function Interfaces
> Version: 3.0.13
> Libs: -L${libdir} -lffi

Looks somewhat sane to me.


> > However here, I see:
> > 
> > PATH=/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/mpfj/buildroot/output/host/usr/bin
> > 
> > So you have /home/mpfj/buildroot/output/host/usr/bin but the failing
> > build takes place in /home/mpjf/buildroot-bt/.
> > 
> > Can you remove /home/mpfj/buildroot/output/host/usr/bin from your PATH
> > and try again?
> > 
> > To be honest, I don't quite see why this would be causing problems, but
> > that's the only possibly "odd" thing that I see in your
> > configuration/setup for the moment.
> 
> Still fails ...

Gaah. So, the next debugging step is:

strace -s 512 -o foo.log -f ./output/host/usr/bin/pkg-config --list-all

and then pastebin the contents of foo.log. We'll see where it looks for
its .pc file, whether it looks or not for libffi.pc, etc.

Thanks :-)

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

[Buildroot] libglib2 (or maybe libffi) build failure

[Mark Jackson]

On 27/11/13 16:51, Thomas Petazzoni wrote:
> Dear Mark Jackson,
> 
> On Wed, 27 Nov 2013 16:45:36 +0000, Mark Jackson wrote:
> 
>>> Ok. What does libffi.pc contains?
>>
>> $ cat output/staging/usr/lib/pkgconfig/libffi.pc 
>> prefix=/usr
>> exec_prefix=/usr
>> libdir=${exec_prefix}/lib
>>
>> Name: libffi
>> Description: Library supporting Foreign Function Interfaces
>> Version: 3.0.13
>> Libs: -L${libdir} -lffi
> 
> Looks somewhat sane to me.
> 
> 
>>> However here, I see:
>>>
>>> PATH=/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/mpfj/buildroot/output/host/usr/bin
>>>
>>> So you have /home/mpfj/buildroot/output/host/usr/bin but the failing
>>> build takes place in /home/mpjf/buildroot-bt/.
>>>
>>> Can you remove /home/mpfj/buildroot/output/host/usr/bin from your PATH
>>> and try again?
>>>
>>> To be honest, I don't quite see why this would be causing problems, but
>>> that's the only possibly "odd" thing that I see in your
>>> configuration/setup for the moment.
>>
>> Still fails ...
> 
> Gaah. So, the next debugging step is:
> 
> strace -s 512 -o foo.log -f ./output/host/usr/bin/pkg-config --list-all
> 
> and then pastebin the contents of foo.log. We'll see where it looks for
> its .pc file, whether it looks or not for libffi.pc, etc.
> 
> Thanks :-)

Aha ... the previous "buildroot" entry in $PATH is the cuplrit.

The foo.log file contains lines such as:-

15616 open("/home/mpfj/buildroot/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/pkgconfig/libcrypto.pc", O_RDONLY)
                       ^^^^^^^^^
I guess it's now in a confused state, so I should do a full clean ?

If so, can you tell me if it's possible to keep 2 different toolchains in use ?

The original "buildroot" path was to my "known-good" buildroot setup (based on
2013.02), but I'm looking to update things to the latest.

I'd rather not destroy my existing toolchain setup, so is it possible to set things
up to handle 2 buildroots at the same time ?

Cheers
Mark J.

[Buildroot] libglib2 (or maybe libffi) build failure

[Thomas Petazzoni]

Dear Mark Jackson,

On Wed, 27 Nov 2013 17:03:20 +0000, Mark Jackson wrote:

> Aha ... the previous "buildroot" entry in $PATH is the cuplrit.

Ok. It's true that having an already existing cross-compiler and
Buildroot installation in the PATH can possibly cause some issues,
though I'd like this to work properly.

> The foo.log file contains lines such as:-
> 
> 15616 open("/home/mpfj/buildroot/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/pkgconfig/libcrypto.pc", O_RDONLY)
>                        ^^^^^^^^^
> I guess it's now in a confused state, so I should do a full clean ?

Can you give us the contents of host/usr/bin/pkg-config ? It is a
wrapper shell script that sets a bunch of variables and calls pkgconf.

I would nonetheless like to have your full "foo.log", to see more
precisely what's going on with pkg-config.

> If so, can you tell me if it's possible to keep 2 different toolchains in use ?
> 
> The original "buildroot" path was to my "known-good" buildroot setup (based on
> 2013.02), but I'm looking to update things to the latest.
> 
> I'd rather not destroy my existing toolchain setup, so is it possible to set things
> up to handle 2 buildroots at the same time ?

It is possible, just don't have one in the PATH in a permanent way. The
way I typically do things is by adjusting the PATH only in the
shell/terminal I'm going to use the toolchain, or even use the full
toolchain path.

Again, I believe we should continue to investigate this some more, I'd
like to understand the root of the problem and see if there's a
reasonable fix for it (even though I believe there might be several
other issues in trying to do a Buildroot build with an existing
Buildroot build in the PATH).

Best regards,

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

[Buildroot] libglib2 (or maybe libffi) build failure

[Mark Jackson]

On 27/11/13 17:16, Thomas Petazzoni wrote:
> Dear Mark Jackson,
> 
> On Wed, 27 Nov 2013 17:03:20 +0000, Mark Jackson wrote:
> 
>> Aha ... the previous "buildroot" entry in $PATH is the cuplrit.
> 
> Ok. It's true that having an already existing cross-compiler and
> Buildroot installation in the PATH can possibly cause some issues,
> though I'd like this to work properly.

Hmmm .. thinking about it, I don't think I did a make clean when I switched
to my new testing branch.

What's the recommended method ?

I recall I did something like:-

[git clone to directory "buildroot"]
$ git checkout 2013.02 -b good
$ make menuconfig
$ make
... build okay ...

Then when I started on the new "updated" branch:-

$ cp -a buildroot buildroot-bt
$ git checkout origin/master -b master
$ git pull
$ make menuconfig
$ make
... build fails ...

I can see now that this might cause all sorts of config issues !!

>> The foo.log file contains lines such as:-
>>
>> 15616 open("/home/mpfj/buildroot/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/pkgconfig/libcrypto.pc", O_RDONLY)
>>                        ^^^^^^^^^
>> I guess it's now in a confused state, so I should do a full clean ?
> 
> Can you give us the contents of host/usr/bin/pkg-config ? It is a
> wrapper shell script that sets a bunch of variables and calls pkgconf.

#!/bin/sh
PKG_CONFIG_LIBDIR=${PKG_CONFIG_LIBDIR:-/home/mpfj/buildroot/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/lib/pkgconfig:/home/mpfj/buildroot/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/share/pkgconfig} PKG_CONFIG_SYSROOT_DIR=${PKG_CONFIG_SYSROOT_DIR:-/home/mpfj/buildroot/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot} $(dirname $0)/pkgconf $@

> I would nonetheless like to have your full "foo.log", to see more
> precisely what's going on with pkg-config.

http://code.bulix.org/p5dd3s-85085

>> If so, can you tell me if it's possible to keep 2 different toolchains in use ?
>>
>> The original "buildroot" path was to my "known-good" buildroot setup (based on
>> 2013.02), but I'm looking to update things to the latest.
>>
>> I'd rather not destroy my existing toolchain setup, so is it possible to set things
>> up to handle 2 buildroots at the same time ?
> 
> It is possible, just don't have one in the PATH in a permanent way. The
> way I typically do things is by adjusting the PATH only in the
> shell/terminal I'm going to use the toolchain, or even use the full
> toolchain path.
> 
> Again, I believe we should continue to investigate this some more, I'd
> like to understand the root of the problem and see if there's a
> reasonable fix for it (even though I believe there might be several
> other issues in trying to do a Buildroot build with an existing
> Buildroot build in the PATH).

Your help is much appreciated.