From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>, "John Snow" <jsnow@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: minimal "zero conf" build dockerfiles for fedora:latest and alpine:latest
Date: Wed, 13 Jan 2021 11:29:23 +0100 [thread overview]
Message-ID: <f6157834-98d7-a49b-9cf9-87c2b15c2a81@redhat.com> (raw)
In-Reply-To: <20210113100956.xuyvmxayh5xytja3@sirius.home.kraxel.org>
On 1/13/21 11:09 AM, Gerd Hoffmann wrote:
> Hi,
>
>> I don't like Perl really, but there's a chicken-and-egg problem between
>> detecting Python and using it to print the configure help script. For
>> configure-time tasks, Perl has the advantage that "#! /usr/bin/env perl"
>> just works.
>
> Assuming perl is actually installed, the world seems to shift to python.
> On a minimal fedora install python is present but perl is not ...
>
> On the other hand git depends on perl, so it is probably pretty hard to
> find a developer workstation without perl installed, so maybe that
> doesn't matter much for the time being.
There is also the new configure-parse-buildoptions.pl script Paolo
wants to add:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg770651.html
next prev parent reply other threads:[~2021-01-13 10:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 22:37 minimal "zero conf" build dockerfiles for fedora:latest and alpine:latest John Snow
2021-01-13 6:48 ` Thomas Huth
2021-01-13 8:26 ` Paolo Bonzini
2021-01-13 10:09 ` Gerd Hoffmann
2021-01-13 10:29 ` Philippe Mathieu-Daudé [this message]
2021-01-13 14:35 ` Paolo Bonzini
2021-01-13 18:31 ` John Snow
2021-01-14 11:10 ` Andrea Bolognani
2021-01-14 16:13 ` John Snow
2021-01-13 18:27 ` John Snow
2021-01-13 8:20 ` Paolo Bonzini
2021-01-13 18:44 ` John Snow
2021-01-14 16:51 ` 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=f6157834-98d7-a49b-9cf9-87c2b15c2a81@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=jsnow@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@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).