qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Scott Wood <scottwood@freescale.com>
Cc: Stefan Weil <sw@weilnetz.de>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] Allow building without graphics support
Date: Thu, 13 Dec 2012 07:31:14 +0100	[thread overview]
Message-ID: <50C97632.80800@weilnetz.de> (raw)
In-Reply-To: <1355359739.28445.22@snotra>

Am 13.12.2012 01:48, schrieb Scott Wood:
> On 12/12/2012 12:46:44 AM, Stefan Weil wrote:
>> Am 12.12.2012 04:18, schrieb Scott Wood:
>>> QEMU is sometimes used in embedded contexts, where graphical support
>>> is unnecessary.  The ability to turn off graphics support not only
>>> saves some space, but it eliminates the dependency on pixman.
>>>
>>> Signed-off-by: Scott Wood <scottwood@freescale.com>
>>> ---
>>> There are undoubtedly some rough edges that need to be cleaned up and
>>> other parts of graphics code that could be compiled out -- this is 
>>> mainly
>>> meant to see what people think of the concept.
>>>
>>> My immediate motivation was that the QEMU-supplied pixman was being a
>>> pain to cross compile (especially without hacking up the generated QEMU
>>> makefiles to pass additional things to pixman's configure), and in
>>> general it would be nice to not have to carry around graphical baggage
>>> when running on hardware that doesn't even have a display (so I was 
>>> more
>>> inclined to do this than to spend effort fixing the pixman build).
>>
>> Hi,
>>
>> cross compilation works for me with the internal pixman.
>> Here is an example which I use to compile Windows 64 bit
>> executables on Debian:
>>
>> ./configure' '--cross-prefix=amd64-mingw32msvc-'
>>
>> Are there still problems with cross compilation in latest QEMU?
>
> It doesn't seem to like my --cross-prefix being a full path rather 
> than being a recognized target pattern:
>
> checking host system type... Invalid configuration 
> `/home/scott/fsl/tc/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnu': 
> machine 
> `/home/scott/fsl/tc/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc' 
> not recognized
> configure: error: /bin/bash /home/scott/fsl/git/qemu/pixman/config.sub 
> /home/scott/fsl/tc/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnu 
> failed
> make: *** [pixman/Makefile] Error 1
>
> When I forced --host=powerpc-linux into the pixman configure command 
> in QEMU's generated Makefile, it got past that, but it built 
> everything with the native compiler:
>
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... powerpc-unknown-linux-gnu
> checking for powerpc-linux-gcc... no
> checking for gcc... gcc
>
> Looking a bit more closely, it seems that it's the QEMU rather than 
> pixman's autoconf that is making the bad assumption about the format 
> of --cross-prefix (I really wasn't up for wading in autoconf).  
> Running basename on cross-prefix and explicitly supplying CC and such 
> to pixman would help, though there still should be a way to pass in an 
> explicit host tuple if you have an unusually-named toolchain.
>
> -Scott

Indeed, --cross-prefixdoes not support absolute path names.

I assume that the executables in
/home/scott/fsl/tc/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/binare 
without prefix
(gcc, ld, ...). Then there must also be the same executables with prefix
(powerpc-linux-gnu-gcc, powerpc-linux-gnu-ld, ...). These must be 
somewhere in PATH.
Use --cross-prefix=powerpc-linux-gnu-(note the "-" at the end).
Then pixman would be configured with --host=powerpc-linux-gnu and should 
find
the compiler. It won't find the compiler powerpc-linux-gcc when its real 
name is
powerpc-linux-gnu-gcc.

-Stefan

  reply	other threads:[~2012-12-13  6:31 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12  3:18 [Qemu-devel] [RFC PATCH] Allow building without graphics support Scott Wood
2012-12-12  6:46 ` Stefan Weil
2012-12-13  0:48   ` Scott Wood
2012-12-13  6:31     ` Stefan Weil [this message]
2012-12-13 15:53       ` Scott Wood
2012-12-13 18:58         ` Stefan Weil
2012-12-13 19:16           ` Scott Wood
2012-12-13 19:32             ` Scott Wood
2012-12-14  8:13             ` Gerd Hoffmann
2012-12-14 18:51               ` Scott Wood
2012-12-19  9:02                 ` Gerd Hoffmann
2012-12-19 18:47                   ` Scott Wood
2012-12-14  8:07         ` Gerd Hoffmann
2012-12-14 18:48           ` Scott Wood
2012-12-19  9:13             ` Gerd Hoffmann
2012-12-19 18:57               ` Scott Wood
2012-12-20  6:59                 ` Gerd Hoffmann
2012-12-20 16:19                   ` Scott Wood
2012-12-21  8:56                     ` Gerd Hoffmann
2012-12-21 10:56                       ` Robert Schiele
2012-12-21 19:01                         ` Scott Wood
2012-12-12  7:52 ` Gerd Hoffmann
2012-12-13  0:57   ` Scott Wood
2012-12-13  7:16     ` Gerd Hoffmann
2012-12-13 14:44       ` Alexander Graf
2012-12-13 15:10         ` Peter Maydell
2012-12-13 15:16         ` Gerd Hoffmann
2012-12-13 15:30           ` Alexander Graf
2012-12-13 15:57           ` Scott Wood
2012-12-12 16:28 ` John Spencer
2012-12-12 16:54   ` Andreas Färber
2012-12-13  0:53     ` Scott Wood
2012-12-12 16:47 ` Peter Maydell
2012-12-12 17:09   ` Andreas Färber
2012-12-12 17:37     ` Peter Maydell
2012-12-12 17:42     ` Paolo Bonzini
2012-12-13  0:51   ` Scott Wood

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=50C97632.80800@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=aliguori@us.ibm.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=scottwood@freescale.com \
    /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).