From: Paolo Bonzini <pbonzini@redhat.com>
To: Brad Smith <brad@comstyle.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] configure: some fixes for OpenBSD
Date: Fri, 24 Aug 2012 14:02:57 +0200 [thread overview]
Message-ID: <50376D71.7070909@redhat.com> (raw)
In-Reply-To: <20120824120053.GQ29273@rox.home.comstyle.com>
Il 24/08/2012 14:00, Brad Smith ha scritto:
>>>>> > >> > OpenBSD's uname works as expected with the -s flag so remove the special
>>>>> > >> > handling when determining the target OS. Use arch -s to retrieve the
>>>>> > >> > hardware architecture as uname -m will return the meta architecture
>>>>> > >> > instead of the hardware architecture (.e.g. macppc vs powerpc).
>>> > > I'm afraid I think this patch is moving in the wrong direction.
>>> > > Wherever possible we should be using compiler checks like check_define,
>>> > > not looking at the output of 'uname' and the like. The former will
>>> > > work when cross compiling, and the latter will give the wrong answers.
>>> > > In some places we have that kind of 'look at uname/etc' check but
>>> > > we should be trying to reduce and eliminate it where possible.
>> >
>> > Right, we should support GNU triplets and a --host argument, and replace
>> > uname checks with pattern matching on the triplet.
> That still requires a means of generating that triplet in the first place.
That's what GNU config.guess is for, but it is only used in the
non-cross-compilation case. QEMU's homegrown configure hardly
distinguishes between native and cross builds.
Paolo
next prev parent reply other threads:[~2012-08-24 12:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 9:47 [Qemu-devel] [PATCH] configure: some fixes for OpenBSD Brad Smith
2012-08-24 9:55 ` Peter Maydell
2012-08-24 10:03 ` Brad Smith
2012-08-24 11:56 ` Paolo Bonzini
2012-08-24 12:00 ` Brad Smith
2012-08-24 12:02 ` Paolo Bonzini [this message]
2012-08-24 12:15 ` Brad Smith
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=50376D71.7070909@redhat.com \
--to=pbonzini@redhat.com \
--cc=brad@comstyle.com \
--cc=peter.maydell@linaro.org \
--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.