From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Weil <sw@weilnetz.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developer <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH for-2.9] Fix check for target OS support
Date: Tue, 28 Mar 2017 13:14:29 +0100 [thread overview]
Message-ID: <CAFEAcA92obh8joN2efLNrrXUD+ga7To1KZR9W3Lt5A0Y-e-qYw@mail.gmail.com> (raw)
In-Reply-To: <7f7dd18e-1fd6-8d11-c446-58e150cd1518@weilnetz.de>
On 28 March 2017 at 13:07, Stefan Weil <sw@weilnetz.de> wrote:
> Am 28.03.2017 um 09:10 schrieb Peter Maydell:
>> On 27 March 2017 at 21:11, Stefan Weil <sw@weilnetz.de> wrote:
>>> *)
>>> - error_exit "Unsupported host OS $targetos"
>>> + supported_os="no"
>> This was deliberately an error_exit because anything
>> going down that path got the Linux defines/includes by
>> accident and we thought that would not work on
>> anything else. What was using it? If we need an extra
>> entry in the case statement we can add one.
>
> It remains an error (that's why I introduced a third state for
> supported_os), but must be handled later, after processing
> a potential --help option.
I think the right fix for this is to special case --help
to bypass more checks and to happen earlier. For instance
if you don't happen to have a 'python' on your PATH then
we do this:
netbsdvm# ./configure --help
ERROR: Python not found. Use --python=/path/to/python
I'll have a go at writing a patch.
thanks
-- PMM
next prev parent reply other threads:[~2017-03-28 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 20:11 [Qemu-devel] [PATCH for-2.9] Fix check for target OS support Stefan Weil
2017-03-28 7:10 ` Peter Maydell
2017-03-28 12:07 ` Stefan Weil
2017-03-28 12:14 ` Peter Maydell [this message]
2017-03-28 8:04 ` Paolo Bonzini
2017-03-28 11:53 ` Stefan Weil
2017-03-28 12:03 ` Peter Maydell
2017-03-28 12:05 ` Mark Cave-Ayland
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=CAFEAcA92obh8joN2efLNrrXUD+ga7To1KZR9W3Lt5A0Y-e-qYw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).