From: Keith Owens <kaos@ocs.com.au>
To: Alexander.Riesen@synopsys.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Announce: Kernel Build for 2.5, Release 2.1 is available
Date: Wed, 24 Apr 2002 08:29:43 +1000 [thread overview]
Message-ID: <16499.1019600983@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Tue, 23 Apr 2002 11:23:31 +0200." <20020423112331.B1142@riesen-pc.gr05.synopsys.com>
On Tue, 23 Apr 2002 11:23:31 +0200,
Alex Riesen <Alexander.Riesen@synopsys.com> wrote:
>Small issue with generation of defkeymap.c:
>i got error that there was no permission to write in the file from
>/bin/sh. Sorry, accidentially typed Ctrl-L in terminal and the error was
>lost. I'll try to reproduce it (it's not every time).
Standard problem when the kernel ships files that are also overwritten
at run time. You get permission problems if the kernel code is marked
read only. After kbuild 2.5 goes in I have a list of FIXME files to
clean up.
>Btw, why it isn't possible to run "make clean installable"?
>Or at least "make clean oldconfig installable"?
Race conditions when running parallel make. With kbuild 2.5 you do not
need to make clean before building, unlike the existing build system,
kbuild 2.5 gets it right.
prev parent reply other threads:[~2002-04-24 0:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 7:43 Announce: Kernel Build for 2.5, Release 2.1 is available Keith Owens
2002-04-21 13:53 ` Keith Owens
2002-04-21 14:32 ` Daniel Phillips
2002-04-22 23:00 ` Keith Owens
2002-04-21 23:04 ` Daniel Phillips
2002-04-22 23:54 ` Keith Owens
2002-04-22 23:57 ` Keith Owens
2002-04-22 14:36 ` Alex Riesen
2002-04-22 23:03 ` Keith Owens
2002-04-23 9:23 ` Alex Riesen
2002-04-23 22:29 ` Keith Owens [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=16499.1019600983@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=Alexander.Riesen@synopsys.com \
--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