[Buildroot] libglib2 (or maybe libffi) build failure

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Wed Nov 27 17:16:56 UTC 2013

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 Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering

More information about the buildroot mailing list