From: Mark Jackson <mpfj-list@newflow.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] libglib2 (or maybe libffi) build failure
Date: Wed, 27 Nov 2013 17:03:20 +0000 [thread overview]
Message-ID: <529625D8.4080507@newflow.co.uk> (raw)
In-Reply-To: <20131127175114.619d17d5@skate>
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.
next prev parent reply other threads:[~2013-11-27 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 15:28 [Buildroot] libglib2 (or maybe libffi) build failure Mark Jackson
2013-11-27 16:15 ` Thomas Petazzoni
2013-11-27 16:25 ` Mark Jackson
2013-11-27 16:37 ` Thomas Petazzoni
2013-11-27 16:45 ` Mark Jackson
2013-11-27 16:51 ` Thomas Petazzoni
2013-11-27 17:03 ` Mark Jackson [this message]
2013-11-27 17:16 ` Thomas Petazzoni
2013-11-27 17:27 ` Mark Jackson
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=529625D8.4080507@newflow.co.uk \
--to=mpfj-list@newflow.co.uk \
--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