From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Should QEMU's configure script check for bzip2 ?
Date: Fri, 8 Nov 2019 11:20:35 +0100 [thread overview]
Message-ID: <839dd7c3-2f28-d00e-c14b-abd507f2296c@redhat.com> (raw)
In-Reply-To: <20191108094856.GD182396@redhat.com>
On 11/8/19 10:48 AM, Daniel P. Berrangé wrote:
> On Thu, Nov 07, 2019 at 08:43:27PM +0100, Thomas Huth wrote:
>>
>> Hi,
>>
>> I just tried to compile QEMU on a freshly installed system. "configure"
>> finished without problems, but during "make" I hit this error:
>>
>> BUNZIP2 pc-bios/edk2-i386-secure-code.fd.bz2
>> /bin/sh: bzip2: command not found
>> make: *** [Makefile:305: pc-bios/edk2-i386-secure-code.fd] Error 127
>> make: *** Deleting file 'pc-bios/edk2-i386-secure-code.fd'
>> make: *** Waiting for unfinished jobs....
>>
>> Sure, it's easy to fix, but maybe "configure" should already check for the
You found a bug :)
>> availablity of "bzip2", so that we then either skip the installation of the
>> edk2 images if "bzip2" is not available, or bail out during "configure"
>> already?
>
> The general rule is that if we run a binary we should check for it upfront
> so users immediately see any missing pre-requisites, rather than wasting
> 30 minutes waiting for QEMU to build & then fail.
Yes, I'll send a fix.
Regards,
Phil.
prev parent reply other threads:[~2019-11-08 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 19:43 Should QEMU's configure script check for bzip2 ? Thomas Huth
2019-11-07 19:59 ` Wainer dos Santos Moschetta
2019-11-08 9:48 ` Daniel P. Berrangé
2019-11-08 10:20 ` Philippe Mathieu-Daudé [this message]
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=839dd7c3-2f28-d00e-c14b-abd507f2296c@redhat.com \
--to=philmd@redhat.com \
--cc=berrange@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).