From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:51377) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TjB89-0007I3-0y for qemu-devel@nongnu.org; Thu, 13 Dec 2012 10:55:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TjB85-0001Pt-US for qemu-devel@nongnu.org; Thu, 13 Dec 2012 10:55:24 -0500 Received: from va3ehsobe006.messaging.microsoft.com ([216.32.180.16]:51876 helo=va3outboundpool.messaging.microsoft.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TjB85-0001Ph-Re for qemu-devel@nongnu.org; Thu, 13 Dec 2012 10:55:21 -0500 Date: Thu, 13 Dec 2012 09:53:18 -0600 From: Scott Wood References: <1355359739.28445.22@snotra> <50C97632.80800@weilnetz.de> In-Reply-To: <50C97632.80800@weilnetz.de> (from sw@weilnetz.de on Thu Dec 13 00:31:14 2012) Message-ID: <1355413998.14046.0@snotra> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; delsp=Yes; format=Flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [RFC PATCH] Allow building without graphics support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil Cc: Anthony Liguori , qemu-devel@nongnu.org, Gerd Hoffmann On 12/13/2012 12:31:14 AM, Stefan Weil wrote: > Am 13.12.2012 01:48, schrieb Scott Wood: >> It doesn't seem to like my --cross-prefix being a full path rather =20 >> than being a recognized target pattern: >>=20 >> checking host system type... Invalid configuration =20 >> `/home/scott/fsl/tc/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powe= rpc-linux-gnu': =20 >> machine =20 >> `/home/scott/fsl/tc/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powe= rpc' =20 >> not recognized >> configure: error: /bin/bash =20 >> /home/scott/fsl/git/qemu/pixman/config.sub =20 >> /home/scott/fsl/tc/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/power= pc-linux-gnu =20 >> failed >> make: *** [pixman/Makefile] Error 1 >>=20 >> When I forced --host=3Dpowerpc-linux into the pixman configure command =20 >> in QEMU's generated Makefile, it got past that, but it built =20 >> everything with the native compiler: >>=20 >> 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 >>=20 >> Looking a bit more closely, it seems that it's the QEMU rather than =20 >> pixman's autoconf that is making the bad assumption about the format =20 >> of --cross-prefix (I really wasn't up for wading in autoconf). =20 >> Running basename on cross-prefix and explicitly supplying CC and =20 >> such to pixman would help, though there still should be a way to =20 >> pass in an explicit host tuple if you have an unusually-named =20 >> toolchain. >>=20 >> -Scott >=20 > Indeed, --cross-prefixdoes not support absolute path names. >=20 > I assume that the executables in > /home/scott/fsl/tc/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/binare =20 > without prefix > (gcc, ld, ...). No, they are with prefix, just not in $PATH. I have more than one =20 "powerpc-linux-gnu" toolchain and I don't want to mess with my $PATH =20 constantly to choose between them. > Then there must also be the same executables with prefix > (powerpc-linux-gnu-gcc, powerpc-linux-gnu-ld, ...). These must be =20 > somewhere in PATH. No. This was never a requirement before -- why now? > Use --cross-prefix=3Dpowerpc-linux-gnu-(note the "-" at the end). > Then pixman would be configured with --host=3Dpowerpc-linux-gnu and =20 > should find > the compiler. It won't find the compiler powerpc-linux-gcc when its =20 > real name is > powerpc-linux-gnu-gcc. No, it's real name is =20 /home/scott/fsl/tc/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-= linux-gnu-gcc -Scott=