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:15:11 +0100 [thread overview]
Message-ID: <20131127171511.2abd4873@skate> (raw)
In-Reply-To: <52960F8C.5040003@newflow.co.uk>
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
next prev parent reply other threads:[~2013-11-27 16:15 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 [this message]
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
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=20131127171511.2abd4873@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