qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: iPXE: update submodule
Date: Mon, 2 Dec 2019 13:31:24 +0100	[thread overview]
Message-ID: <eb8cc032-25bb-75c3-8043-bc1e68ef895a@redhat.com> (raw)
In-Reply-To: <20191202121853.shigtyrko725vmmg@sirius.home.kraxel.org>

On 12/2/19 1:18 PM, Gerd Hoffmann wrote:
> On Mon, Dec 02, 2019 at 12:19:50PM +0100, Philippe Mathieu-Daudé wrote:
>> Hi Gerd,
>>
>> 'make -C roms efirom' is failing on Fedora 30.
>>
>> Can you update the iPXE submodule so we get these buildsys commits:
>>
>> c742c576 [build] Move predefined all-drivers build shortcut to Makefile
>> a4f8c6e3 [build] Do not apply WORKAROUND_CFLAGS for host compiler
>> 1dd56dbd [build] Workaround compilation error with gcc 9.1
>> 412acd78 [build] Fix "'%s' directive argument is null" error
> 
> Hmm.  Sure, can do that, but the question is for 4.2 or 5.0.  Updating
> ipxe that close to the release makes me nervous, but shipping a ipxe
> version which doesn't build with recent compilers in the release tarball
> isn't great either.
> 
> I'd tend to go the 5.0 route.

I think 5.0 is OK, because if distributions build it, the are probably 
already backporting these patches, so they can backport the QEMU patch 
instead.



      parent reply	other threads:[~2019-12-02 12:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 11:19 iPXE: update submodule Philippe Mathieu-Daudé
2019-12-02 12:18 ` Gerd Hoffmann
2019-12-02 12:24   ` Thomas Huth
2019-12-02 12:31   ` Philippe Mathieu-Daudé [this message]

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=eb8cc032-25bb-75c3-8043-bc1e68ef895a@redhat.com \
    --to=philmd@redhat.com \
    --cc=kraxel@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).