From: Anthony Liguori <aliguori@us.ibm.com>
To: Paul Brook <paul@codesourcery.com>
Cc: Jan Kiszka <jan.kiszka@web.de>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] Re: [PATCH] Drop roms from standard build
Date: Thu, 09 Jul 2009 12:11:50 -0500 [thread overview]
Message-ID: <4A5624D6.8060007@us.ibm.com> (raw)
In-Reply-To: <200907091808.06764.paul@codesourcery.com>
Paul Brook wrote:
>>> I think the chances of the user having appropriate toolchains readily
>>> available (without significant additional per-rom configury) are
>>> extremely slim.
>>>
>> Actually, for x86, all of our ROMs will just use GCC so when building
>> x86 on x86, it's very likely the right tool chain is available.
>>
>
> Except when it isn't, for example when building with a windows binary.
>
That's a simple problem that has to do with the way ld is being used. A
patch was posted that actually works with the mingw ld.
> Also, x86 is only one of many targets qemu supports. If you're serious about
> rebuilding roms as standard, then at bare minimum you need to handle sparc and
> ppc as well as x86.
>
Yup. That's why we need to probe for toolchains in order to determine
whether roms can be built. If you're a developer making changes to
OpenBIOS, clearly you are going to have the appropriate tool chains
installed.
> Paul
>
--
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-07-09 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 7:12 [Qemu-devel] [PATCH] Drop roms from standard build Jan Kiszka
2009-07-09 7:52 ` [Qemu-devel] " Alexander Graf
2009-07-09 11:19 ` Jan Kiszka
2009-07-09 15:42 ` Anthony Liguori
2009-07-09 16:19 ` Paul Brook
2009-07-09 16:59 ` Anthony Liguori
2009-07-09 17:08 ` Paul Brook
2009-07-09 17:11 ` Anthony Liguori [this message]
2009-07-09 17:34 ` Paul Brook
2009-07-09 19:33 ` Filip Navara
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=4A5624D6.8060007@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=agraf@suse.de \
--cc=jan.kiszka@web.de \
--cc=paul@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.