From: Oleg Verych <olecom@flower.upol.cz>
To: Linus Torvalds <torvalds@osdl.org>, Sam Ravnborg <sam@ravnborg.org>
Cc: kbuild <kbuild-devel@lists.sourceforge.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: [patch] kbuild: create KBUILD_OUTPUT
Date: Wed, 24 Jan 2007 00:53:06 +0000 [thread overview]
Message-ID: <20070124005305.GA30155@flower.upol.cz> (raw)
kbuild: create KBUILD_OUTPUT
When requesting build to another directory, try to create it first.
Cc: Sam Ravnborg <sam@ravnborg.org>
Signed-off-by: Oleg Verych <olecom@flower.upol.cz>
---
,-*- bash -*-
|olecom@deen:~/kernel.org/_work/src/linux-2.6.20-rc5$
|olecom@deen:~/kernel.org/_work/src/linux-2.6.20-rc5$ make O=/tmp/build
|cd: 1: can't cd to /tmp/build
|Makefile:116: *** output directory "/tmp/build" does not exist. Stop.
|olecom@deen:~/kernel.org/_work/src/linux-2.6.20-rc5$ patch -p1 <../../va-patch/
|kbuild-create-output-dir.patch
|patching file Makefile
|olecom@deen:~/kernel.org/_work/src/linux-2.6.20-rc5$ make O=/tmp/build
|HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/docproc make[3]: ***
|[scripts/basic/docproc] Interrupt make[2]: *** [scripts_basic] Interrupt
|make: *** [_all] Interrupt
|
|olecom@deen:~/kernel.org/_work/src/linux-2.6.20-rc5$
`-*-
--- linux-2.6.20-rc5/Makefile~orig 2007-01-12 19:54:26.000000000 +0100
+++ linux-2.6.20-rc5/Makefile 2007-01-24 00:59:55.926951750 +0100
@@ -113,5 +113,5 @@
# check that the output directory actually exists
saved-output := $(KBUILD_OUTPUT)
-KBUILD_OUTPUT := $(shell cd $(KBUILD_OUTPUT) && /bin/pwd)
+KBUILD_OUTPUT := $(shell d=$(KBUILD_OUTPUT) ; mkdir -p $$d && cd $$d && pwd)
$(if $(KBUILD_OUTPUT),, \
$(error output directory "$(saved-output)" does not exist))
reply other threads:[~2007-01-24 0:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070124005305.GA30155@flower.upol.cz \
--to=olecom@flower.upol.cz \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®