All of lore.kernel.org
 help / color / mirror / Atom feed
* [RFC] standard KBUILD_OUTPUT filesystem location?
@ 2004-01-19  9:51 Peter Johanson
  0 siblings, 0 replies; only message in thread
From: Peter Johanson @ 2004-01-19  9:51 UTC (permalink / raw)
  To: linux-kernel; +Cc: x86-kernel, spyderous, strider

[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]

(please CC me on any replies, as i'm not subscribed)

Q: If one were to have to pick a "standard" place to assign
KBUILD_OUTPUT in the top level Makefile, where would it be?

In particular, Gentoo has been having problems with compiling external
modules against 2.6 kernels, as most of the time this results in
attempting to write to the source tree, and our sandbox system
preventing this and dying.

After smashing my head against the wall for about a month, I've been
working on a experimental system to *always* set KBUILD_OUTPUT, so
there's always a clean source tree to compile against using the
recommended "make -C /usr/src/linux/ SUBDIRS=/foo O=some/tmp/dir"
(setting O= without a clean kernel source tree just causes kbuild to
yell at you to run "make mrproper")

The details of this discussion can be found on our bugzilla here:
http://bugs.gentoo.org/show_bug.cgi?id=32737

So, where would you put the "default kernel output"?

The general concensus so far has been /var/tmp/kernel-output/${KV} (KV
is the kernel version, e.g. 2.6.1-mm4)

Comments? feedback? "what a horrible idea"s ?

-pete

-- 
Peter Johanson
<latexer@gentoo.org>

Key ID = 0x6EFA3917
Key fingerprint = A90A 2518 57B1 9D20 9B71  A2FF 8649 439B 6EFA 3917

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2004-01-19 21:46 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-01-19  9:51 [RFC] standard KBUILD_OUTPUT filesystem location? Peter Johanson

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.