From: Paolo Bonzini <bonzini@gnu.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Glauber Costa <glommer@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Alexander Graf <agraf@suse.de>,
Filip Navara <filip.navara@gmail.com>,
Jan Ondrej <ondrejj@salstar.sk>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] Fix checksum writing in signboot.sh
Date: Mon, 03 Aug 2009 08:12:00 +0200 [thread overview]
Message-ID: <4A767FB0.2030607@gnu.org> (raw)
In-Reply-To: <4A764BD3.1070003@codemonkey.ws>
>> Right. In fact we just switched from C to sh for portability reasons.
>
> The problem is with cross compilers. Our build system is based around a
> single tool chain and we only do feature probing, sanity checking,
> cflags modifications, etc. on the target tool chain. If we build and run
> a C program using the host compiler (which is needed in order to be able
> to run the program), things get complicated quickly.
One hopes that you do not need feature tests for the build compiler if
it is used for someting as simple as generating checksums. The build
compiler should be just "cc" or "gcc".
That said, I don't think sh is a big problem.
Paolo
next prev parent reply other threads:[~2009-08-03 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 9:48 [Qemu-devel] [PATCH] Fix checksum writing in signboot.sh Alexander Graf
2009-08-02 10:04 ` [Qemu-devel] " Avi Kivity
2009-08-02 10:25 ` Filip Navara
2009-08-02 11:15 ` Avi Kivity
2009-08-02 11:58 ` Alexander Graf
2009-08-02 12:21 ` Avi Kivity
2009-08-02 21:29 ` [Qemu-devel] " Sebastian Herbszt
2009-08-03 2:30 ` [Qemu-devel] " Anthony Liguori
2009-08-03 6:12 ` Paolo Bonzini [this message]
2009-08-03 12:55 ` Avi Kivity
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=4A767FB0.2030607@gnu.org \
--to=bonzini@gnu.org \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=filip.navara@gmail.com \
--cc=glommer@redhat.com \
--cc=ondrejj@salstar.sk \
--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).