From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Problem building libglib2
Date: Fri, 30 Nov 2012 09:37:07 +0100 [thread overview]
Message-ID: <50B87033.7090609@mind.be> (raw)
In-Reply-To: <20121130001154.129b9238@skate>
On 30/11/12 00:11, Thomas Petazzoni wrote:
> Dear Arnout Vandecappelle,
>
> On Thu, 29 Nov 2012 21:27:56 +0100, Arnout Vandecappelle wrote:
>
>> We could obviously solve this by unexporting PKG_CONFIG_SYSROOT_DIR, but
>> perhaps the better approach is to remove those environment variables from our
>> custom pkgconf?
>
> No, we use PKG_CONFIG_SYSROOT_DIR="/" when we build packages for the
> host, so we can't simply remove support for the PKG_CONFIG_SYSROOT_DIR
> environment variable. Unexporting PKG_CONFIG_SYSROOT_DIR sounds like
> the good solution here.
Right.
Charles, would you care to prepare a patch that unexports PKG_CONFIG_SYSROOT_DIR
and test it in your angstrom environment?
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
next prev parent reply other threads:[~2012-11-30 8:37 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
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 [this message]
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=50B87033.7090609@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox