From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joshua Lock <joshua.lock@collabora.co.uk>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] oe-init-build-env: fix for build dirs that have spaces in their path
Date: Mon, 13 Apr 2015 17:34:16 +0100 [thread overview]
Message-ID: <1428942856.6976.81.camel@linuxfoundation.org> (raw)
In-Reply-To: <1428939002-21170-1-git-send-email-joshua.lock@collabora.co.uk>
On Mon, 2015-04-13 at 16:30 +0100, Joshua Lock wrote:
> Enclose expansions of BUILDDIR in quotes in order to correctly handle paths
> which include spaces.
>
> Signed-off-by: Joshua Lock <joshua.lock@collabora.co.uk>
Autotools cannot handle things with spaces so whilst this will fix the
environment setup part, I think you'll see sanity check warnings in
short order?
I did once start fixing this until I found it meant fixing auto* at
which point I gave up.
Cheers,
Richard
prev parent reply other threads:[~2015-04-13 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 15:30 [PATCH] oe-init-build-env: fix for build dirs that have spaces in their path Joshua Lock
2015-04-13 16:34 ` Richard Purdie [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=1428942856.6976.81.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=joshua.lock@collabora.co.uk \
--cc=openembedded-core@lists.openembedded.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