I unpacked a new kernel tree, patched up to 2.4.19-pre10-ac2. I then applied
the kbuild-2.5 patch for this version (from stingr), and did a make
oldconfig/make installable/make install. Everything went just fine.
I rebooted, and decided to make some changes to the config. I went back into
the source tree, and renamed Makefile to Makefile-2.4 and Makefile-2.5 to
Makefile (so I don't have to keep specifying -f Makefile-2.5). I then did
"make menuconfig", and turned on loadable module support and the kernel
module loader. After the configuration got saved, kbuild automatically
started a "make installable" pass! Although I was planning on doing this
anyway, I don't think was expected behavior.
> <snip>?
> ... and renamed Makefile to Makefile-2.4 and Makefile-2.5 to
> Makefile (so I don't have to keep specifying -f Makefile-2.5).
You are not supposed to do this. The original Makefile gets grepped
for kernel version by kbuild 2.5. Your renaming the Makefiles is probably
the cause of the seemingly automated rebuild.
T.
OK, my bad. I won't shoot myself in the foot again.
----- Original Message -----
From: "Tomas Szepe" <[email protected]>
To: "Kevin P. Fleming" <[email protected]>
Cc: <[email protected]>
Sent: Thursday, June 06, 2002 12:15 PM
Subject: Re: kbuild-2.5 2.4.19-pre10-ac2 "automatic" make installable?
> > <snip>?
> > ... and renamed Makefile to Makefile-2.4 and Makefile-2.5 to
> > Makefile (so I don't have to keep specifying -f Makefile-2.5).
>
> You are not supposed to do this. The original Makefile gets grepped
> for kernel version by kbuild 2.5. Your renaming the Makefiles is probably
> the cause of the seemingly automated rebuild.
>
> T.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>