All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Bug 1817345 <1817345@bugs.launchpad.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug 1817345] Re: configure script breaks when $source_path contains white spaces
Date: Sun, 24 Feb 2019 19:54:23 +0000	[thread overview]
Message-ID: <CAFEAcA8Lti+JrJ=Fh=k8D7Tqt=dE2YQSjyisVXU=rXWF=zqWBA@mail.gmail.com> (raw)
In-Reply-To: <155103713660.11385.8973225882401821375.malone@gac.canonical.com>

On Sun, 24 Feb 2019 at 19:46, Michael Tokarev
<1817345@bugs.launchpad.net> wrote:
> I think it is better to just disallow building in a path containing
> spaces, -- there are so many packages and other tools that fails in this
> config, might require lots of work to fix this AND to ensure all future
> changes are still working, and there's an easy workaround

Certainly I bet that the problems with spaces in the path do
not stop with the handling of the target-list help message.
Make does not really get on at all with spaces...
It would probably be helpful if we made configure complain
if it finds spaces in the build or source paths.

thanks
-- PMM

  reply	other threads:[~2019-02-24 19:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 16:26 [Qemu-devel] [Bug 1817345] [NEW] configure script breaks when $source_path contains white spaces Antonio Ospite
2019-02-24 19:38 ` [Qemu-devel] [Bug 1817345] " Michael Tokarev
2019-02-24 19:54   ` Peter Maydell [this message]
2019-02-25  7:36 ` Antonio Ospite
2019-03-09 19:16 ` Deepika Choudhary
2019-03-09 20:54 ` Peter Maydell
2019-03-10  3:46   ` Deepika Choudhary
2019-05-03 17:26 ` Peter Maydell
2019-08-02 17:46 ` Peter Maydell
2019-08-16  4:59 ` Thomas Huth

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='CAFEAcA8Lti+JrJ=Fh=k8D7Tqt=dE2YQSjyisVXU=rXWF=zqWBA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=1817345@bugs.launchpad.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.