From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] libglib2 (or maybe libffi) build failure
Date: Wed, 27 Nov 2013 17:51:14 +0100 [thread overview]
Message-ID: <20131127175114.619d17d5@skate> (raw)
In-Reply-To: <529621B0.60106@newflow.co.uk>
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
next prev parent reply other threads:[~2013-11-27 16:51 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 [this message]
2013-11-27 17:03 ` Mark Jackson
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=20131127175114.619d17d5@skate \
--to=thomas.petazzoni@free-electrons.com \
--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