All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Problem building libglib2
Date: Thu, 29 Nov 2012 19:22:14 +0100	[thread overview]
Message-ID: <50B7A7D6.5090607@mind.be> (raw)
In-Reply-To: <20121129190813.5dc97298@skate>

On 29/11/12 19:08, Thomas Petazzoni wrote:
> Dear Charles Manning,
>
> On Fri, 30 Nov 2012 06:52:44 +1300, Charles Manning wrote:
>>>    Maybe there's something fishy in your environment.  Can you run
>>> env | grep /lib
>>
>> Aaaarrrrggghhhh!!!!
>>
>> I have this system set up to automatically set up for openembedded.
>>   That defines PKG_CONFIG_PATH and adds some stuff to PATH which is probably
>> messing things up.
>>
>> I turned off the openembedded auto configuration, nuked output/ and make ran
>> to completion.
>>
>> I have now also learned a lot more about digging around in buildroot.
>
> Wait, wait, could you please reproduce the problem, and reply to
> Arnout's questions (sending us the output of env | grep /lib, or even
> the entire output of env if it doesn't contain any sensitive
> information).
>
> I would like to this which environment variable was causing the
> problem, and if we can add a check in Buildroot for this environment
> variable, in order to avoid similar issues in the future.

  After a second look in config.log:

pkg_cv_DBUS1_CFLAGS='-I/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/include/dbus-1.0 
-I/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib/dbus-1.0/include  '
pkg_cv_DBUS1_LIBS='-L/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib -ldbus-1 -lpthread -lrt  '
pkg_cv_LIBFFI_CFLAGS=' '
pkg_cv_LIBFFI_LIBS='-L/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib -lffi  '
pkg_cv_ZLIB_CFLAGS='-I/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/include  '
pkg_cv_ZLIB_LIBS='-L/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/lib -lz  '


  I really don't see how this can happen: we unexport PKG_CONFIG_PATH and set
PKG_CONFIG explicitly in the Makefile...

  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-11-29 18:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28  1:37 [Buildroot] Problem building libglib2 Charles Manning
2012-11-28 13:31 ` Thomas Petazzoni
2012-11-28 18:09   ` Charles Manning
2012-11-28 21:59     ` Arnout Vandecappelle
     [not found]       ` <201211291121.46456.manningc2@actrix.gen.nz>
2012-11-29  9:28         ` Arnout Vandecappelle
2012-11-29 17:52           ` Charles Manning
2012-11-29 18:08             ` Thomas Petazzoni
2012-11-29 18:22               ` Arnout Vandecappelle [this message]
2012-11-29 18:31               ` Charles Manning
2012-11-29 20:27                 ` Arnout Vandecappelle
2012-11-29 23:11                   ` Thomas Petazzoni
2012-11-30  8:37                     ` Arnout Vandecappelle
2012-12-02 22:42                       ` Charles Manning
2014-08-22 14:13                         ` oscarin
2014-08-24 21:04                           ` Thomas Petazzoni

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=50B7A7D6.5090607@mind.be \
    --to=arnout@mind.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.