From: Michal Marek <mmarek@suse.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: kbuild: global makefile and spaces in path
Date: Wed, 6 Jan 2016 15:48:07 +0100 [thread overview]
Message-ID: <568D2927.2010106@suse.com> (raw)
In-Reply-To: <87lh8nfrx8.fsf@belgarion.home>
On 2015-12-21 21:49, Robert Jarzmik wrote:
> Hi Michal,
>
> I compiled my kernel in a directory /home/robert jarzmik/kernel, and that's the
> first time I encountered a space in the path containing my kernel in years.
>
> I was wondering if there is a known constraint that the linux kernel source
> should be contained within a path without any space ?
Whitespace and colons are problematic.
> If no such constraint is known, maybe you could consider the patch in [1].
I expect it is going to break in lot more places, especially if you do
an O= build. I think it's better to just check for this and error out early.
Michal
next prev parent reply other threads:[~2016-01-06 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 20:49 kbuild: global makefile and spaces in path Robert Jarzmik
2016-01-06 14:48 ` Michal Marek [this message]
2016-01-07 21:53 ` Robert Jarzmik
2016-02-05 21:30 ` Robert Jarzmik
2016-02-08 20:03 ` Michal Marek
2016-02-08 20:10 ` Robert Jarzmik
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=568D2927.2010106@suse.com \
--to=mmarek@suse.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
/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.