From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: Thomas Huth <thuth@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Laszlo Ersek" <lersek@redhat.com>
Subject: Re: Should QEMU's configure script check for bzip2 ?
Date: Thu, 7 Nov 2019 17:59:03 -0200 [thread overview]
Message-ID: <313ea616-7ce4-2427-9f80-f489bf13d612@redhat.com> (raw)
In-Reply-To: <da6cfaeb-420e-6e84-ca14-a75d900d65c0@redhat.com>
On 11/7/19 5:43 PM, 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....
This error happened with me a few times as well. And I always wondered
why bzip2 isn't checked on configure.
>
>
> Sure, it's easy to fix, but maybe "configure" should already check for
> the 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?
IMHO, it should be checked since bzip2 is a build dependency.
Thanks,
Wainer
>
>
> Thomas
>
>
next prev parent reply other threads:[~2019-11-07 20:00 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 [this message]
2019-11-08 9:48 ` Daniel P. Berrangé
2019-11-08 10:20 ` Philippe Mathieu-Daudé
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=313ea616-7ce4-2427-9f80-f489bf13d612@redhat.com \
--to=wainersm@redhat.com \
--cc=lersek@redhat.com \
--cc=philmd@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).