From: Gerd Hoffmann <kraxel@redhat.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Stefan Weil <sw@weilnetz.de>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH] Allow building without graphics support
Date: Wed, 19 Dec 2012 10:13:34 +0100 [thread overview]
Message-ID: <50D1853E.7040803@redhat.com> (raw)
In-Reply-To: <1355510914.4740.3@snotra>
Hi,
>> # ls -l /usr/bin/*-gcc
>> -rwxr-xr-x. 2 root root 264112 Aug 23 2011 /usr/bin/i686-pc-mingw32-gcc
>> -rwxr-xr-x. 2 root root 268216 Oct 18 18:24
>> /usr/bin/x86_64-redhat-linux-gcc
>>
>> I think the second part ("pc" / "redhat") can be choosen pretty freely
>> when building gcc, so you could name your cross compilers differently,
>> then have them in PATH and pick by name instead of typing full paths.
>
> For the most part I don't build these toolchains, so that's not an
> option.
Ok.
> Plus, I like having each toolchain fully contained in its own
> directory.
No need to change that, you can just stick all the directories into the
PATH. Well, you could if the different compilers would have different
names, thats why I suggested that ...
>> ./configure
>> --cross-prefix=/home/scott/fsl/tc/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnu-
>>
>> && make ?
>
> A few more options than that, but basically yes.
>
> I can get past this particular obstacle by doing something like:
>
> (PATH=/home/scott/.../powerpc-linux-gnu/bin:"$PATH" ./configure
> --cross-prefix=powerpc-linu-gnu- ...)
Why do you need this? Any tools not picked up correctly if you don't
set the PATH? Which ones?
> ...but then I run into the problem that --extra-cflags and
> --extra-ldflags don't get passed into pixman.
That should be fixable easily. Have a patch for that? If so, please
send to the list. Otherwise I can have a look.
Why do you need --extra-cflags + --extra-ldflags btw?
cheers,
Gerd
next prev parent reply other threads:[~2012-12-19 9:13 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
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 [this message]
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=50D1853E.7040803@redhat.com \
--to=kraxel@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=scottwood@freescale.com \
--cc=sw@weilnetz.de \
/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).