qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Yoder Stuart-B08248 <B08248@freescale.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	David Gibson <dwg@au1.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 04/25] Add hard build dependency on glib
Date: Wed, 27 Jul 2011 18:54:09 +1000	[thread overview]
Message-ID: <1311756849.25044.668.camel@pasglop> (raw)
In-Reply-To: <4E2F3B33.6080100@us.ibm.com>


> 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.

Well, that hard requirement is causing us problem on our 32/64-bit cross
builds as well.

It looks like glib (at least recent versions in -sid) can't be built
64-bit on a 32-bit system :-( At least not without fixing some horrid
bugs in there related to some generated include path from what David
says (I'll let him comment further).

In general, every time you add a library requirement without some config
option to disable it for cases such as ours, you add pain :-)

Now, in the specific case of glib, I understand why you would want to
get rid of re-invented wheels and use it, so I'm not specifically
criticizing that specific change, we'll eventually have to fix it
anyways. Just a heads up to be careful with hard requirements in
general.

Cheers,
Ben.

  reply	other threads:[~2011-07-27  8:54 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
2011-07-27  8:54         ` Benjamin Herrenschmidt [this message]
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=1311756849.25044.668.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=B08248@freescale.com \
    --cc=aliguori@us.ibm.com \
    --cc=dwg@au1.ibm.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).