From: Gerd Hoffmann <kraxel@suse.de>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: kbuild: problems with separate src/obj trees
Date: Mon, 23 Jan 2006 14:15:52 +0100 [thread overview]
Message-ID: <43D4D708.2050802@suse.de> (raw)
Hi,
Trapped into two problems with 2.6.16-rc1:
(1) Building kernels with the source tree on a r/o filesystem
doesn't work any more because kbuild tries to create
$(srctree)/.kernelrelease and fails to do so.
(2) UML kernels don't build at all with a separate obj tree:
master-xen kraxel ~/objtree/vanilla-2.6.16-pre-um# make ARCH=um
gmake -C /home/kraxel/scratch/vanilla-2.6.16-pre
O=/home/kraxel/objtree/vanilla-2.6.16-pre-um
SYMLINK arch/um/include/kern_constants.h
ln: creating symbolic link `arch/um/include/kern_constants.h' to
`../../../include/asm-um/asm-offsets.h': No such file or directory
gmake[2]: *** [arch/um/include/kern_constants.h] Error 1
gmake[1]: *** [cdbuilddir] Error 2
gmake: *** [all] Error 2
Ideas/Patches anyone?
Gerd
--
Gerd 'just married' Hoffmann <kraxel@suse.de>
I'm the hacker formerly known as Gerd Knorr.
http://www.suse.de/~kraxel/just-married.jpeg
next reply other threads:[~2006-01-23 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 13:15 Gerd Hoffmann [this message]
2006-01-23 15:15 ` kbuild: problems with separate src/obj trees Kalin KOZHUHAROV
2006-01-23 16:46 ` Gerd Hoffmann
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=43D4D708.2050802@suse.de \
--to=kraxel@suse.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