From: Markus Elfring <Markus.Elfring@web.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Check handling of kernel build output directory
Date: Sat, 27 Oct 2007 07:07:55 +0200 [thread overview]
Message-ID: <ffuh39$d7b$1@ger.gmane.org> (raw)
In-Reply-To: <20071026194727.GA23871@uranus.ravnborg.org>
> You did it in your output directory I assume.
No.
> kbuild complains that the source directory is not clean - which
> is what you need to clean up.
I am looking for the real reasons for the occuring error messages. Let us look at another
test example ...
Sonne:~ # ls -ld /usr/src/linux
lrwxrwxrwx 1 root root 23 Oct 13 10:11 /usr/src/linux -> /usr/src/linux-2.6.23.1
Sonne:~ # cd /usr/src/linux-2.6.23.1
Sonne:/usr/src/linux-2.6.23.1 # unset KBUILD_OUTPUT && make mrproper && cp -p
/boot/config-2.6.23.1-0-adjusted .config && export
KBUILD_OUTPUT=/usr/src/obj/linux/2.6.23.1/x86_64/adjusted && rm -rf $KBUILD_OUTPUT/*
CLEAN .config
Sonne:/usr/src/linux-2.6.23.1 # make oldconfig && date && echo
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX && make -j2 && echo
YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY && make -j2 modules_install install && echo
ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ && date
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
GEN /usr/src/obj/linux/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 -o arch/x86_64/Kconfig
*
* Linux Kernel Configuration
*
*
* General setup
*
[...]
#
# configuration written to .config
#
Sat Oct 27 06:43:24 CEST 2007
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
GEN /usr/src/obj/linux/2.6.23.1/x86_64/adjusted/Makefile
scripts/kconfig/conf -s arch/x86_64/Kconfig
GEN /usr/src/obj/linux/2.6.23.1/x86_64/adjusted/Makefile
CHK include/linux/version.h
UPD include/linux/version.h
CHK include/linux/utsrelease.h
UPD include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86_64
Using /usr/src/linux-2.6.23.1 as source for kernel
/usr/src/linux-2.6.23.1 is not clean, please run 'make mrproper'
in the '/usr/src/linux-2.6.23.1' directory.
make[1]: *** [prepare3] Error 1
make: *** [_all] Error 2
make: INTERNAL: Exiting with 3 jobserver tokens available; should be 2!
Which files are not clean in my situation after the command "make mrproper" was executed
at the beginning?
Which results do you or other software developers get by such test runs on kernel releases
since "2.6.22.9-0.4-default" like it is published by SUSE now?
( I can build the current Linux kernel into my source directory successfully.)
Regards,
Markus
next prev parent reply other threads:[~2007-10-27 5:08 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 [this message]
2007-10-27 7:23 ` Sam Ravnborg
2007-10-27 12:30 ` Markus Elfring
2007-10-27 16:00 ` Markus Elfring
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='ffuh39$d7b$1@ger.gmane.org' \
--to=markus.elfring@web.de \
--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