From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/docker
Date: Tue, 08 Jul 2008 08:40:55 +0200 [thread overview]
Message-ID: <877ibwvpxk.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20080708054144.507E03C67C@busybox.net> (ulf@uclibc.org's message of "Mon\, 7 Jul 2008 22\:41\:44 -0700 \(PDT\)")
>>>>> "ulf" == ulf <ulf@uclibc.org> writes:
ulf> Author: ulf
ulf> Date: 2008-07-07 22:41:44 -0700 (Mon, 07 Jul 2008)
ulf> New Revision: 22682
ulf> Log:
ulf> Add glib2.0 specific include/pkconfig paths in 'docker'
ulf> Modified:
ulf> trunk/buildroot/package/docker/docker.mk
..
ulf> DOCKER_MAKE_OPT = CC=$(TARGET_CC) CXX=$(TARGET_CXX) LD=$(TARGET_LD) \
ulf> - CFLAGS="-I$(STAGING_DIR)/usr/include" \
ulf> + CFLAGS="-I$(STAGING_DIR)/usr/include \
ulf> + -I$(STAGING_DIR)/usr/include/glib-2.0 \
ulf> + -I$(STAGING_DIR)/usr/lib/glib-2.0/include" \
ulf> LDFLAGS="-L$(STAGING_DIR)/usr/lib -L$(STAGING_DIR)/lib" \
ulf> PKGCONFIG="$(STAGING_DIR)/usr/bin/pkg-config" \
ulf> - PKG_CONFIG_SYSROOT="$(STAGING_DIR)"
ulf> + PKG_CONFIG_SYSROOT="$(STAGING_DIR)" \
ulf> + PKG_CONFIG_PATH="$(STAGING_DIR)/usr/lib/pkgconfig"
Is all of this needed? And shouldn't it be PKG_CONFIG_SYSROOT_DIR
instead? We don't use the pkgconfig wrapper anymore.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-07-08 6:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 5:41 [Buildroot] svn commit: trunk/buildroot/package/docker ulf at uclibc.org
2008-07-08 6:40 ` Peter Korsgaard [this message]
2008-07-08 9:25 ` Ulf Samuelsson
2008-07-08 9:52 ` Peter Korsgaard
2008-07-08 10:01 ` Ulf Samuelsson
-- strict thread matches above, loose matches on Subject: below --
2008-10-26 9:14 jacmet at uclibc.org
2008-10-26 9:14 jacmet at uclibc.org
2008-10-26 9:14 jacmet at uclibc.org
2008-05-02 11:20 ninevoltz at uclibc.org
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=877ibwvpxk.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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