From: Laurent Vivier <laurent@vivier.eu>
To: Antonio Ospite <antonio.ospite@collabora.com>,
Peter Maydell <peter.maydell@linaro.org>,
Eric Blake <eblake@redhat.com>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Antonio Ospite <ao2@ao2.it>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH v2 2/2] configure: disallow spaces and colons in source path and build path
Date: Wed, 22 May 2019 17:21:14 +0200 [thread overview]
Message-ID: <87d49db7-68c7-7c2e-7464-47e335013e58@vivier.eu> (raw)
In-Reply-To: <9349da74-b4a1-932d-227a-a63df1bb63a5@collabora.com>
On 22/05/2019 17:01, Antonio Ospite wrote:
> On 22/05/19 15:57, Laurent Vivier wrote:
>> On 09/05/2019 16:42, Peter Maydell wrote:
>>> On Mon, 6 May 2019 at 18:27, Eric Blake <eblake@redhat.com> wrote:
>>>>
>>>> On 5/3/19 3:27 AM, Antonio Ospite wrote:
>>>>> From: Antonio Ospite <antonio.ospite@collabora.com>
>>>>>
>>>>> The configure script breaks when the qemu source directory is in a
>>>>> path
>>>>> containing white spaces, in particular the list of targets is not
>>>>> correctly generated when calling "./configure --help" because of
>>>>> how the
>>>>> default_target_list variable is built.
>>>>>
>>>>> In addition to that, *building* qemu from a directory with spaces
>>>>> breaks
>>>>> some assumptions in the Makefiles, even if the original source path
>>>>> does
>>>>> not contain spaces like in the case of an out-of-tree build, or when
>>>>> symlinks are involved.
>>>>>
>>>>> To avoid these issues, refuse to run the configure script and the
>>>>> Makefile if there are spaces or colons in the source path or the build
>>>>> path, taking as inspiration what the kbuild system in linux does.
>>>>>
>>>>> Buglink: https://bugs.launchpad.net/qemu/+bug/1817345
>>>>>
>>>>> Signed-off-by: Antonio Ospite <antonio.ospite@collabora.com>
>>>>> ---
>>>>> Makefile | 4 ++++
>>>>> configure | 6 ++++++
>>>>> 2 files changed, 10 insertions(+)
>>>>>
>>>>
>>>>> +++ b/Makefile
>>>>> @@ -1,5 +1,9 @@
>>>>> # Makefile for QEMU.
>>>>>
>>>>> +ifneq ($(words $(subst :, ,$(CURDIR))), 1)
>>>>> + $(error main directory cannot contain spaces nor colons)
>>>>> +endif
>>>>> +
>>>>> # Always point to the root of the build tree (needs GNU make).
>>>>> BUILD_DIR=$(CURDIR)
>>>>>
>>>>> diff --git a/configure b/configure
>>>>> index 9832cbca5c..f7ad4381bd 100755
>>>>> --- a/configure
>>>>> +++ b/configure
>>>>> @@ -279,6 +279,12 @@ ld_has() {
>>>>> # make source path absolute
>>>>> source_path=$(cd "$(dirname -- "$0")"; pwd)
>>>>>
>>>>> +if printf "%s\n" "$source_path" | grep -q "[[:space:]:]" ||
>>>>> + printf "%s\n" "$PWD" | grep -q "[[:space:]:]";
>>>>
>>>> For less typing and fewer processes, you could shorten this to:
>>>>
>>>> if printf %s\\n "$source_path" "$PWD" | grep -q "[[:space:]:]";
>>>>
>>>> but that's trivial enough for a maintainer to fold in if desired.
>>>>
>>>> Reviewed-by: Eric Blake <eblake@redhat.com>
>>>
>>> What tree is this going to go in via? I suggest the
>>> -trivial tree.
>>
>>
>> Applied (unchanged) to my trivial-patches branch.
>>
>
> Thank you Laurent.
>
> I'll think about sending a followup patch with the changes proposed by
> Eric and I'll CC you if I do.
If you want to send a v3 of this patch to update it, I can wait.
Thanks,
Laurent
next prev parent reply other threads:[~2019-05-22 15:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 8:27 [Qemu-devel] [PATCH v2 0/2] configure: disallow spaces and colons in source path and build path Antonio Ospite
2019-05-03 8:27 ` Antonio Ospite
2019-05-03 8:27 ` [Qemu-devel] [PATCH v2 1/2] configure: set source_path only once and make its definition more robust Antonio Ospite
2019-05-03 8:27 ` Antonio Ospite
2019-05-06 17:23 ` Eric Blake
2019-05-03 8:27 ` [Qemu-devel] [PATCH v2 2/2] configure: disallow spaces and colons in source path and build path Antonio Ospite
2019-05-03 8:27 ` Antonio Ospite
2019-05-06 17:27 ` Eric Blake
2019-05-06 20:23 ` Antonio Ospite
2019-05-09 14:42 ` Peter Maydell
2019-05-22 13:57 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
2019-05-22 15:01 ` Antonio Ospite
2019-05-22 15:21 ` Laurent Vivier [this message]
2019-05-22 15:26 ` Antonio Ospite
2019-05-22 15:37 ` Laurent Vivier
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=87d49db7-68c7-7c2e-7464-47e335013e58@vivier.eu \
--to=laurent@vivier.eu \
--cc=antonio.ospite@collabora.com \
--cc=ao2@ao2.it \
--cc=eblake@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).