From: Olaf Hering <olaf@aepfle.de>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, "Igor Mammedov" <imammedo@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-4.0 v2 2/2] roms: Allow the EDK2_EFIROM variable to be overridden
Date: Wed, 10 Apr 2019 08:25:54 +0200 [thread overview]
Message-ID: <20190410082554.6c595b3f.olaf@aepfle.de> (raw)
In-Reply-To: <fbf6f219-4821-67be-27b2-42a0bad9746a@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
Am Mon, 8 Apr 2019 13:05:07 +0200
schrieb Laszlo Ersek <lersek@redhat.com>:
> Then build scripts could be updated to invoke:
>
> make -C roms \
> EDK2_BASETOOLS_OPTFLAGS='...' \
> EDK2_BASETOOLS_LDFLAGS='...' \
> efirom
The question remains: 'But why?'.
Why can edk2 not be built with '-fno-pie' right away?
Did noone approach the edk2 developers yet that their buildsystem is broken in that regard?
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Olaf Hering <olaf@aepfle.de>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "Igor Mammedov" <imammedo@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-4.0 v2 2/2] roms: Allow the EDK2_EFIROM variable to be overridden
Date: Wed, 10 Apr 2019 08:25:54 +0200 [thread overview]
Message-ID: <20190410082554.6c595b3f.olaf@aepfle.de> (raw)
Message-ID: <20190410062554.DkJnCcdKFP3ie9uYx4cgV61z6EI_JR_a4GEhGtX5Ui4@z> (raw)
In-Reply-To: <fbf6f219-4821-67be-27b2-42a0bad9746a@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
Am Mon, 8 Apr 2019 13:05:07 +0200
schrieb Laszlo Ersek <lersek@redhat.com>:
> Then build scripts could be updated to invoke:
>
> make -C roms \
> EDK2_BASETOOLS_OPTFLAGS='...' \
> EDK2_BASETOOLS_LDFLAGS='...' \
> efirom
The question remains: 'But why?'.
Why can edk2 not be built with '-fno-pie' right away?
Did noone approach the edk2 developers yet that their buildsystem is broken in that regard?
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-04-10 6:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 15:33 [Qemu-devel] [PATCH for-4.0 v2 0/2] roms: Rename the EFIROM variable and let it be overridable Philippe Mathieu-Daudé
2019-04-05 15:33 ` Philippe Mathieu-Daudé
2019-04-05 15:33 ` [Qemu-devel] [PATCH for-4.0 v2 1/2] roms: Rename the EFIROM variable to avoid clashing with iPXE Philippe Mathieu-Daudé
2019-04-05 15:33 ` Philippe Mathieu-Daudé
2019-04-08 10:54 ` Laszlo Ersek
2019-04-08 10:54 ` Laszlo Ersek
2019-04-05 15:33 ` [Qemu-devel] [PATCH for-4.0 v2 2/2] roms: Allow the EDK2_EFIROM variable to be overridden Philippe Mathieu-Daudé
2019-04-05 15:33 ` Philippe Mathieu-Daudé
2019-04-08 11:05 ` Laszlo Ersek
2019-04-08 11:05 ` Laszlo Ersek
2019-04-10 6:25 ` Olaf Hering [this message]
2019-04-10 6:25 ` Olaf Hering
2019-04-10 14:54 ` Laszlo Ersek
2019-04-10 14:54 ` Laszlo Ersek
2019-04-08 9:02 ` [Qemu-devel] [PATCH for-4.0 v2 0/2] roms: Rename the EFIROM variable and let it be overridable Laszlo Ersek
2019-04-08 9:02 ` Laszlo Ersek
2019-04-08 9:20 ` Laszlo Ersek
2019-04-08 9:20 ` Laszlo Ersek
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=20190410082554.6c595b3f.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@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).