qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Yoder Stuart-B08248 <B08248@freescale.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 04/25] Add hard build dependency on glib
Date: Tue, 26 Jul 2011 17:09:55 -0500	[thread overview]
Message-ID: <4E2F3B33.6080100@us.ibm.com> (raw)
In-Reply-To: <9F6FE96B71CF29479FF1CDC8046E15031876FA@039-SN1MPN1-002.039d.mgd.msft.net>

On 07/26/2011 04:51 PM, Yoder Stuart-B08248 wrote:
>
> I am having issues with this in a cross compilation
> environment.   In Power embedded, almost all our
> development is using cross toolchains.
>
> Neither glib or pkg-config are in our cross build environment
> and I'm having issues getting them built and installed.
> Not even sure if pkg-config is even supposed to work
> in a cross development environment...I'm new to that
> tool and poking around a bit with google raises
> some questions.

You're probably setting up your cross environment incorrectly which, 
unfortunately, is very common.

The proper thing to do is to have GCC use a different system include 
directory and a different prefix.  That will result in a directory where 
there are gcc binaries with normal names installed in ${cross_prefix}/bin

You need to build and install pkg-config to this prefix too, and then 
when it comes time to actually doing the QEMU configure, you should do 
something like:

export PATH=${cross_prefix}/bin:$PATH
export PKG_CONFIG_PATH=${cross_prefix}/lib/pkg-config:$PKG_CONFIG_PATH

Many automated cross compiler environment scripts will install specially 
named versions of gcc and binutils in your normal $PATH.  The trouble 
is, this is a bit of a hack and unless you know to make this hack work 
with other build tools, it all comes tumbling down.

Regards,

Anthony Liguori

>
> Wanted to make you aware of the issue...
>
> Stuart
>

  reply	other threads:[~2011-07-26 22:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26  8:59 [Qemu-devel] [PATCH v2 0/1] The intro for QEMU disk I/O limits Zhi Yong Wu
2011-07-26  8:59 ` [Qemu-devel] [PATCH v2 1/1] The codes V2 " Zhi Yong Wu
2011-07-26 19:26   ` Marcelo Tosatti
2011-07-26 21:51     ` [Qemu-devel] [PATCH 04/25] Add hard build dependency on glib Yoder Stuart-B08248
2011-07-26 22:09       ` Anthony Liguori [this message]
2011-07-27  8:54         ` Benjamin Herrenschmidt
2011-07-27 13:31           ` David Gibson
2011-07-27 13:13         ` Yoder Stuart-B08248
2011-07-27 10:17     ` [Qemu-devel] [PATCH v2 1/1] The codes V2 for QEMU disk I/O limits Zhi Yong Wu
2011-07-27 12:58       ` Stefan Hajnoczi
2011-07-28  2:35         ` Zhi Yong Wu
2011-07-28  5:43         ` Zhi Yong Wu
2011-07-28  8:20           ` Stefan Hajnoczi
2011-07-28  8:25             ` Stefan Hajnoczi
2011-07-28  8:50               ` Zhi Yong Wu
2011-07-27 15:49       ` Marcelo Tosatti
2011-07-28  4:24         ` Zhi Yong Wu
2011-07-28 14:42           ` Marcelo Tosatti
2011-07-29  2:09             ` Zhi Yong Wu
  -- strict thread matches above, loose matches on Subject: below --
2011-07-21 20:00 [Qemu-devel] [PULL 0/25]: QMP queue Luiz Capitulino
2011-07-21 20:00 ` [Qemu-devel] [PATCH 04/25] Add hard build dependency on glib Luiz Capitulino
2011-08-02  2:03   ` TeLeMan
2011-08-02 19:06     ` Luiz Capitulino
2011-08-02 19:18       ` Anthony Liguori

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=4E2F3B33.6080100@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=B08248@freescale.com \
    --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).