From: Keith Owens <kaos@ocs.com.au>
To: tomas szepe <kala@pinerecords.com>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: kbuild 2.5 release 2.4
Date: Sat, 04 May 2002 01:57:26 +1000 [thread overview]
Message-ID: <15755.1020441446@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 03 May 2002 17:45:54 +0200." <20020503154554.GB15883@louise.pinerecords.com>
On Fri, 3 May 2002 17:45:54 +0200,
tomas szepe <kala@pinerecords.com> wrote:
>$ make -f Makefile-2.5 menuconfig
>[enable RAMDISK support, tweak ramdisk size, enable initrd]
>...
>
>Now, issuing "M installable" will result in nearly all files getting rebuilt.
>The same happens when switching ramdisk off again. How's that?
>
>I tried enabling/disabling many other config options and doing rebuilds but
>couldn't find anything as damaging buildtime-wise as the ramdisk stuff.
CONFIG_BLK_DEV_INITRD is tested in include/linux/fs.h. Because of the
messy kernel include files, a config change to fs.h affects hundreds of
other files and forces lots of rebuilds. This is a separate problem
from kbuild, other people are looking at cleaning up the include files.
next prev parent reply other threads:[~2002-05-03 15:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 14:19 Keith Owens
2002-05-03 14:37 ` your mail tomas szepe
2002-05-03 15:07 ` tomas szepe
2002-05-03 15:29 ` Keith Owens
2002-05-03 15:45 ` tomas szepe
2002-05-03 15:57 ` Keith Owens [this message]
2002-05-03 16:41 ` kbuild 2.5 release 2.4 tomas szepe
2002-05-04 10:58 ` tomas szepe
2002-05-04 11:24 ` Keith Owens
2002-05-04 11:26 ` Zwane Mwaikambo
2002-05-04 12:11 ` Keith Owens
2002-05-04 11:58 ` Zwane Mwaikambo
2002-05-04 16:21 ` rddunlap
2002-05-04 11:39 ` tomas szepe
2002-05-04 12:00 ` Keith Owens
2002-05-04 12:15 ` tomas szepe
2002-05-04 16:19 ` rddunlap
2002-05-04 16:29 ` Tomas Szepe
2002-05-04 16:30 ` rddunlap
2002-05-05 2:27 ` Keith Owens
2002-05-04 13:01 ` Announce: Kernel Build for 2.5, Release 2.4 is available Keith Owens
2002-05-06 6:27 ` Keith Owens
2002-05-07 17:47 ` [kbuild-devel] " Thomas Duffy
2002-05-09 11:45 ` Keith Owens
2002-05-10 1:46 ` [kbuild-devel] " Thomas Duffy
2002-05-10 3:21 ` Keith Owens
2002-05-11 9:32 ` Keith Owens
2002-05-14 0:12 ` [kbuild-devel] " Thomas Duffy
2002-05-14 2:44 ` Keith Owens
2002-05-14 5:44 ` Keith Owens
2002-05-15 3:46 ` [kbuild-devel] " Thomas Duffy
2002-05-15 13:20 ` Keith Owens
2002-05-17 4:07 ` Keith Owens
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=15755.1020441446@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=kala@pinerecords.com \
--cc=kbuild-devel@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).