All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Arkadiusz Miskiewicz <arekm@pld-linux.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel buildsystem broken on RO medium
Date: Wed, 7 Jan 2004 21:43:45 +0100	[thread overview]
Message-ID: <20040107204345.GA2812@mars.ravnborg.org> (raw)
In-Reply-To: <200401070951.27249.arekm@pld-linux.org>

> Wow now works but tell me, how to do make mrproper if /usr/src/linux-2.6.1 is really read-only?
> I'm asking because I want to build rpms with kernel modules from non-root and root can have
> non-mrproper state in /usr/src/linux-2.6.1.

There is no way to do this, other than take a copy of the SRC.
It was not possible to let kbuild support building a kernel when the kernel
tree contained generated files.
I do not remember the details, but the main issue was with generated .c
files. If a generated .c file were present in the kernel src, it would
not be generated aging in the separate output directory.
Usually this is not too much of a big deal, but it could result in potential
erros later on.
There were also problems with _shipped support and generated .h files,
but I do not recall the details.

In the 2.7 timeframe I plan to be a bit more restrictive on use of -I
directive to gcc, hereby hopefully enabling more consistent behaviour
all over the kernel.

	Sam

      reply	other threads:[~2004-01-07 20:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06 23:41 kernel buildsystem broken on RO medium Arkadiusz Miskiewicz
2004-01-07  6:16 ` Sam Ravnborg
2004-01-07  8:51   ` Arkadiusz Miskiewicz
2004-01-07 20:43     ` Sam Ravnborg [this message]

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=20040107204345.GA2812@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=arekm@pld-linux.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 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.