From: Mason <mpeg.blue@free.fr>
To: LKML <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Embedded white space in out-of-tree module full pathname
Date: Tue, 27 Jan 2015 10:44:41 +0100 [thread overview]
Message-ID: <54C75E09.6050002@free.fr> (raw)
Hello,
I'd like some confirmation that this is either not supported, or that
I'm doing something obviously wrong. (Kernel 3.14 if it matters.)
Suppose the source code for an out-of-tree kernel module is stored e.g.
in "/tmp/foo bar/module" (note the embedded space in the path name)
Here is the Makefile template I'm using. (Maybe it's wrong.)
/tmp/foo bar/module$ cat Makefile
KDIR ?= /home/mason/linux-3.14
ARCH ?= arm
CROSS_COMPILE ?= arm-none-linux-gnueabi-
obj-m += mytest.o
all:
make -C $(KDIR) M="$$PWD"
clean:
make -C $(KDIR) M="$$PWD" clean
/tmp/foo bar/module$ make
make -C /home/mason/linux-3.14 M="$PWD"
make[1]: Entering directory `/home/mason/linux-3.14'
scripts/Makefile.build:44: /tmp/foo/Makefile: No such file or directory
make[2]: *** No rule to make target `/tmp/foo/Makefile'. Stop.
make[1]: *** [_module_/tmp/foo] Error 2
make[1]: Leaving directory `/home/mason/linux-3.14'
make: *** [all] Error 2
Does the kernel build system support building an out-of-tree module whose
full pathname contains embedded white space, like in my example?
Do I have an obvious mistake in my Makefile?
Regards.
next reply other threads:[~2015-01-27 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 9:44 Mason [this message]
2015-01-27 22:39 ` Embedded white space in out-of-tree module full pathname Russell King - ARM Linux
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=54C75E09.6050002@free.fr \
--to=mpeg.blue@free.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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