From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
sam@ravnborg.org, linux-kbuild@vger.kernel.org
Subject: separate object directories: trap for user
Date: Thu, 21 Feb 2008 14:16:28 +0100 [thread overview]
Message-ID: <20080221131628.GA5332@elf.ucw.cz> (raw)
Hi!
I'm using separate object directories, but there's trap there which
catches me every now and then:
(/data/l/linux are my sources, objects are in /data/l/b-linux)
Every now and then, I make a mistake and try to make kernel in source
directories... that does not work as expected:
pavel@amd:/data/l/linux$ time make
scripts/kconfig/conf -s arch/x86/Kconfig
***
*** You have not yet configured your kernel!
*** (missing kernel .config file)
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by
`include/config/kernel.release'. Stop.
0.55user 0.44system 8.15 (0m8.157s) elapsed 12.30%CPU
pavel@amd:/data/l/linux$
...but it has unexpected side effect of breaking build in object
directories:
pavel@amd:/data/l/b-linux$ time make
make -C /data/l/linux O=/data/l/b-linux/.
Using /data/l/linux as source for kernel
/data/l/linux is not clean, please run 'make mrproper'
in the '/data/l/linux' directory.
make[2]: *** [prepare3] Error 1
make[1]: *** [sub-make] Error 2
make: *** [all] Error 2
0.24user 0.18system 5.03 (0m5.032s) elapsed 8.42%CPU
pavel@amd:/data/l/b-linux$
This is needed to fix the situation:
pavel@amd:/data/l/linux$ rmdir include/config/
Would it be possible to stop the oldconfig before it creates
include/config?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
reply other threads:[~2008-02-21 13:16 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=20080221131628.GA5332@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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®