From: John Snow <jsnow@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: minimal "zero conf" build dockerfiles for fedora:latest and alpine:latest
Date: Wed, 13 Jan 2021 13:44:59 -0500 [thread overview]
Message-ID: <9d5478ef-a46c-83e7-0b02-abcf723cb885@redhat.com> (raw)
In-Reply-To: <c1e768d9-24fe-f414-f684-1b1c908c09ce@redhat.com>
On 1/13/21 3:20 AM, Paolo Bonzini wrote:
> On 12/01/21 23:37, John Snow wrote:
>> - our configure file suggests bzip2 is an optional dependency (It's
>> set to 'auto') but meson will error out if it is not present at
>> configuration time:
>>
>> ../pc-bios/meson.build:5:2: ERROR: Program 'bzip2' not found
>
> Yes, the configure option is for libbzip2, not bzip2.
>
> Perhaps bzip2 could be required only if get_option('install_blobs') is
> true, I don't know.
>
Oh, right. Library vs tool. Good point.
Yes, we should make the tool required somewhere in the configure jungle.
>> FROM alpine:latest
>>
>> ENV PACKAGES \
>> wget \
>> xz \
>> python3 \
>> ninja \
>> gcc \
>> musl-dev \
>> pkgconfig \
>> glib-dev \
>> pixman-dev \
>> make \
>> bash \
>> perl
>>
>> ENV QEMU_CONFIGURE_OPTS --disable-linux-user
>>
>> RUN apk add $PACKAGES
>>
>> RUN wget https://download.qemu.org/qemu-5.2.0.tar.xz && \
>> tar xvJf qemu-5.2.0.tar.xz
>>
>> WORKDIR /qemu-5.2.0
>> RUN ./configure $QEMU_CONFIGURE_OPTS && \
>> make -j9
>
> This should be added to the CI!
>
Apparently someone else is working on an Alpine linux patchset, so I
suppose something like this will be included there.
If not, feel free to take it:
Signed-off-by: John Snow <jsnow@redhat.com>
However, yes, I would like to include some build smoke tests for CI,
which just cover "configure && make" with the absolute minimum set of
dependencies possible. We could rebase our more fully fledged tests on
top of them to share the common layer.
Not a priority for me, but I'm keeping these little dinky dockerfiles
around to use as smoke tests against fedora:latest, alpine:latest, etc.
I should likely expand to CentOS stream, debian, and so on to catch
early breakages.
>> - diffutils is required for the qapi-schema test, which runs at build
>> time.
>
> This is not required by meson because technically it is not needed
> except for "make check".
>
Is that true? I was just running "make". qapi-schema test does run at
build time to make sure that the schema pre-processing occurred correctly.
> Perhaps we could do
>
> -if build_docs
> +if build_docs and diff.found()
>
> in tests/qapi-schema/meson.build.
>
> Paolo
>
I wasn't building docs, I don't think. (No sphinx and no --enable-docs.)
--js
next prev parent reply other threads:[~2021-01-13 18:49 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é
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 [this message]
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=9d5478ef-a46c-83e7-0b02-abcf723cb885@redhat.com \
--to=jsnow@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--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 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).