From: Laszlo Ersek <lersek@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Olaf Hering" <olaf@aepfle.de>,
qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1] Makefile: remove DESTDIR from firmware file content
Date: Wed, 5 Jun 2019 18:31:18 +0200 [thread overview]
Message-ID: <33ae1318-9019-62d2-3718-143c9ac5bd9a@redhat.com> (raw)
In-Reply-To: <3e79c06b-cffb-977d-1f08-f1bb46dad795@redhat.com>
On 06/05/19 16:46, Philippe Mathieu-Daudé wrote:
> [Odd, I'm pretty sure I replied to this last week but can't find it, so
> again]
> Cc'ing Laszlo since he wrote this.
>
> On 5/30/19 9:28 PM, Olaf Hering wrote:
>> The resulting firmware files should only contain the runtime path.
>> Fixes commit 26ce90fde5c ("Makefile: install the edk2 firmware images
>> and their descriptors")
>>
>> Signed-off-by: Olaf Hering <olaf@aepfle.de>
>> ---
>> Makefile | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Makefile b/Makefile
>> index f0be624f47..61267bf1a4 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -844,7 +844,7 @@ ifneq ($(DESCS),)
>> $(INSTALL_DIR) "$(DESTDIR)$(qemu_datadir)/firmware"
>> set -e; tmpf=$$(mktemp); trap 'rm -f -- "$$tmpf"' EXIT; \
>> for x in $(DESCS); do \
>> - sed -e 's,@DATADIR@,$(DESTDIR)$(qemu_datadir),' \
>> + sed -e 's,@DATADIR@,$(qemu_datadir),' \
>
> I'm fine with this patch.
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>
> Laszlo, did you use the full path for a particular reason?
Yes. The reason was that I had no idea what DESTDIR stood for. After
grepping the QEMU source tree for DESTDIR, I *still* have no idea what
it stands for.
DESTDIR seems to be an installation prefix that is not controlled through
./configre --prefix=...
Based on memories from other projects -- with better documentation --
though, DESTDIR looks like an install-time-only pre-prefix. In that
sense, the patch looks correct (and the vague expression "runtime path"
in the commit message starts to make some sense). Presumably DESTDIR is
used in package build scripts... Yup, the RHEL spec files use it too,
for "make install".
So, the patch is correct IMO:
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Too bad QEMU is chronically under-documented (and the commit message on
the patch doesn't help much in that regard).
Thanks
Laszlo
>> "$(SRC_PATH)/pc-bios/descriptors/$$x" > "$$tmpf"; \
>> $(INSTALL_DATA) "$$tmpf" \
>> "$(DESTDIR)$(qemu_datadir)/firmware/$$x"; \
>>
next prev parent reply other threads:[~2019-06-05 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 19:28 [Qemu-devel] [PATCH v1] Makefile: remove DESTDIR from firmware file content Olaf Hering
2019-06-05 14:07 ` Daniel P. Berrangé
2019-06-05 14:46 ` Philippe Mathieu-Daudé
2019-06-05 16:31 ` Laszlo Ersek [this message]
2019-06-05 16:45 ` 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=33ae1318-9019-62d2-3718-143c9ac5bd9a@redhat.com \
--to=lersek@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=olaf@aepfle.de \
--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).