From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>, "Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org,
"Richard W . M . Jones" <rjones@redhat.com>
Subject: Re: [PATCH] docker: Base Fedora MinGW cross containers on the base Fedora image
Date: Thu, 4 Mar 2021 14:18:13 +0000 [thread overview]
Message-ID: <YEDsJUKudKJvZA7K@redhat.com> (raw)
In-Reply-To: <138832dc-9340-2a9f-1dc8-b20cc0637c5e@redhat.com>
On Thu, Mar 04, 2021 at 03:00:04PM +0100, Philippe Mathieu-Daudé wrote:
> On 3/3/21 1:46 PM, Daniel P. Berrangé wrote:
> > On Wed, Mar 03, 2021 at 01:42:22PM +0100, Philippe Mathieu-Daudé wrote:
> >> The only difference between fedora-winXX-cross.docker and
> >> fedora.docker is the specific QEMU_CONFIGURE_OPTS environment
> >> variable. All the rest can be inherited from the generic Fedora
> >> image.
> >
> > This is relying on the base Fedora image already having the
> > mingw packages installed. My series to automate creation of
> > the container dockerfiles removes those entirely, so we have
> > strictly separate native and mingw images for Fedora:
> >
> > https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg03123.html
>
> I'm a bit confused. So instead of having one single big image,
> you prefer to have multiple ones.
>
> I stopped using the fedora-winXX-cross because they lacks ccache,
> and the "big" fedora image contains the mingwXX toolchains.
>
> I'll wait you respin your series and test the new created containers
> to see if they fit my needs.
ccache will be present in any of the containers I auto-generate for
QEMU using lcitool, as I agree its a very useful part o fthe toolchain.
So when i convert the winXXX-cross containers, they'll gain ccache
(and alot of other missing mingw pieces)
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-03-04 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 12:42 [PATCH] docker: Base Fedora MinGW cross containers on the base Fedora image Philippe Mathieu-Daudé
2021-03-03 12:46 ` Daniel P. Berrangé
2021-03-04 14:00 ` Philippe Mathieu-Daudé
2021-03-04 14:18 ` Daniel P. Berrangé [this message]
2021-03-04 15:11 ` 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=YEDsJUKudKJvZA7K@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--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).