qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Andrea Bolognani <abologna@redhat.com>, Laszlo Ersek <lersek@redhat.com>
Cc: qemu-devel@nongnu.org, Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH-for-5.0] roms/edk2-funcs.sh: Use available GCC for ARM/Aarch64 targets
Date: Thu, 5 Dec 2019 18:04:52 +0100	[thread overview]
Message-ID: <f5bafdb9-137d-a77e-edc3-dd61d669cdee@redhat.com> (raw)
In-Reply-To: <ea6fdfcaef35ed6571c4234b9400a75b429c72ac.camel@redhat.com>

On 12/5/19 5:47 PM, Andrea Bolognani wrote:
> On Thu, 2019-12-05 at 17:27 +0100, Philippe Mathieu-Daudé wrote:
>> On 12/5/19 5:13 PM, Laszlo Ersek wrote:
>>> If that rules out CentOS 7 as a QEMU project build / CI platform for the
>>> bundled ArmVirtQemu binaries, then we need a more recent platform
>>> (perhaps CentOS 8, not sure).
>>
>> Unfortunately CentOS 8 is not available as a Docker image, which is a
>> convenient way to build EDK2 in a CI.
> 
> Uh?
> 
>    https://hub.docker.com/_/centos
> 
> seems to disagree with you. Is the 'centos:8' image not suitable
> for some non-obvious reason?

Eh, last time I checked	I had an issue with docker, it was working with 
podman but CI don't provide podman.

I tested again, and now it seems to work, I'll give it another try.
gcc-aarch64-linux-gnu is still older than GCC5 although.

Thanks for the update :)

Phil.



  reply	other threads:[~2019-12-05 17:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 22:12 [PATCH-for-5.0] roms/edk2-funcs.sh: Use available GCC for ARM/Aarch64 targets Philippe Mathieu-Daudé
2019-12-05 16:13 ` Laszlo Ersek
2019-12-05 16:27   ` Philippe Mathieu-Daudé
2019-12-05 16:47     ` Andrea Bolognani
2019-12-05 17:04       ` Philippe Mathieu-Daudé [this message]
2019-12-05 16:50     ` Ard Biesheuvel
2019-12-05 19:35       ` Laszlo Ersek
2019-12-06  5:07         ` Philippe Mathieu-Daudé
2019-12-08 17:44           ` dann frazier

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=f5bafdb9-137d-a77e-edc3-dd61d669cdee@redhat.com \
    --to=philmd@redhat.com \
    --cc=abologna@redhat.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=lersek@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).