From: Stuart yoder <stuart.yoder@freescale.com>
To: anthony@codemonkey.ws, qemu-devel@nongnu.org
Cc: Stuart Yoder <stuart.yoder@freescale.com>
Subject: [Qemu-devel] [PATCH] remove cross prefix from pkg-config command
Date: Tue, 2 Aug 2011 15:21:13 -0500 [thread overview]
Message-ID: <1312316473-22591-1-git-send-email-stuart.yoder@freescale.com> (raw)
From: Stuart Yoder <stuart.yoder@freescale.com>
the host pkg-config tool should be used with the location to
pkg-config *.pc files being specified via the PKG_CONFIG_PATH
Signed-off-by: Stuart Yoder <stuart.yoder@freescale.com>
---
The Freescale cross build environment is multilib which
means there are special library paths for different
cpu types. pkg-config installed along with the
other cross tools does not work...it has no clue how
to find the right libraries. So using cross-prefix
does no good. Only thing I can get to work is
explicitly setting PKG_CONFIG_PATH before running
configure.
Not sure how other cross build envionments work, but
it seems like the above method should be sufficiently
general.
configure | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/configure b/configure
index 38e3724..59f6e09 100755
--- a/configure
+++ b/configure
@@ -223,7 +223,7 @@ objcopy="${cross_prefix}${OBJCOPY-objcopy}"
ld="${cross_prefix}${LD-ld}"
strip="${cross_prefix}${STRIP-strip}"
windres="${cross_prefix}${WINDRES-windres}"
-pkg_config="${cross_prefix}${PKG_CONFIG-pkg-config}"
+pkg_config="${PKG_CONFIG-pkg-config}"
sdl_config="${cross_prefix}${SDL_CONFIG-sdl-config}"
# default flags for all hosts
--
1.7.3.4
next reply other threads:[~2011-08-02 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 20:21 Stuart yoder [this message]
2011-08-02 21:01 ` [Qemu-devel] [PATCH] remove cross prefix from pkg-config command Stefan Weil
2011-08-03 6:41 ` Paolo Bonzini
2011-08-03 14:03 ` Yoder Stuart-B08248
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=1312316473-22591-1-git-send-email-stuart.yoder@freescale.com \
--to=stuart.yoder@freescale.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).