From: Markus Elfring <Markus.Elfring@web.de>
To: linux-kernel@vger.kernel.org
Cc: linux-kbuild@vger.kernel.org
Subject: Re: Check handling of kernel build output directory
Date: Sat, 27 Oct 2007 18:00:35 +0200 [thread overview]
Message-ID: <472360A3.8020504@web.de> (raw)
In-Reply-To: <20071027072348.GA28566@uranus.ravnborg.org>
>> Which files are not clean in my situation after the command "make mrproper" was executed
>> at the beginning?
> If you look at the top-level Makefile you will see:
>
> @echo ' Using $(srctree) as source for kernel'
> $(Q)if [ -f $(srctree)/.config -o -d $(srctree)/include/config ]; then \
> echo " $(srctree) is not clean, please run 'make mrproper'";\
> echo " in the '$(srctree)' directory.";\
> /bin/false; \
> fi;
>
> So you either a .config file or the config directory.
Well, I've thought about another viewpoint. The Makefile insists on the detail that no
configuration files are allowed in the source directory if an output directory was specified.
Original wording:
"...
# prepare3 is used to check if we are building in a separate output directory,
# and if so do:
# 1) Check that make has not been executed in the kernel src $(srctree)
..."
I seems now that my troubles came from the missing decision when to move or delete the
.config file from my source directory. So the following command sequence works for a
completely clean build. (It can be adjusted to support parallel configurations for
debug/release situations as usual.)
elfring@Sonne:~/Projekte/Linux/Kernel/2.6.23.1> unset KBUILD_OUTPUT && make mrproper && cp
-p /boot/config-2.6.23.1-0-adjusted .config && export
KBUILD_OUTPUT=~/Projekte/Linux/Kernel/obj/2.6.23.1/x86_64/adjusted && rm -rf
$KBUILD_OUTPUT/* && make silentoldconfig && rm .config && date && echo
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX && make -j4 && echo
YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY && date
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
GEN /home/elfring/Projekte/Linux/Kernel/obj/2.6.23.1/x86_64/adjusted/Makefile
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/kxgettext.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/lex.zconf.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf -s arch/x86_64/Kconfig
Sa 27. Okt 17:37:38 CEST 2007
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
GEN /home/elfring/Projekte/Linux/Kernel/obj/2.6.23.1/x86_64/adjusted/Makefile
[...]
YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
Sa 27. Okt 17:55:09 CEST 2007
Regards,
Markus
next prev parent reply other threads:[~2007-10-27 16:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 17:31 Check handling of kernel build output directory Markus Elfring
2007-10-26 17:36 ` Vegard Nossum
2007-10-26 18:40 ` Markus Elfring
2007-10-26 19:05 ` Markus Elfring
2007-10-27 11:32 ` Jan Engelhardt
2007-10-27 12:21 ` Sam Ravnborg
2007-10-26 19:05 ` Sam Ravnborg
2007-10-26 19:25 ` Markus Elfring
2007-10-26 19:47 ` Sam Ravnborg
2007-10-27 5:07 ` Markus Elfring
2007-10-27 7:23 ` Sam Ravnborg
2007-10-27 12:30 ` Markus Elfring
2007-10-27 16:00 ` Markus Elfring [this message]
2007-10-27 11:33 ` Jan Engelhardt
2007-10-27 12:41 ` Markus Elfring
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=472360A3.8020504@web.de \
--to=markus.elfring@web.de \
--cc=linux-kbuild@vger.kernel.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