On Fri, 22 Jun 2001 21:05:23 -0400,
"Eric S. Raymond" <[EMAIL PROTECTED]> wrote:
>Linus has let the cat out of the bag that 2.5 "looks like it will open
>in a week or two" <http://lwn.net/daily/2.5-coming.php3>.
>So, one big question is, what order are we going to send our patches
>in? Do we want CML2 in first, or new makefiles in first? I don't
>care, personally, but I'd like to have a path mapped out.
I have scheduled this weekend to add the last little bits to the 2.5
Makefiles and generate a patch against 2.4.6-pre5, ready for 2.5. I
see some long hours coming up :).
The current code supports the CML1 utilities because I do my testing on
2.4 kernels. I held off on adding support for CML2 because it was
still changing (Adventure yet!), planning to add CML2 support once the
makefile changes had stabilized. But given Linus's comments it is now
time to add CML2 support. I will not have time until later this
week, if anybody wants to help they can
* Get the kbuild-2.4.3 patch set from
http://prdownloads.sourceforge.net/kbuild/kbuild-2.4.3.gz
* Get the latest CML2.
* Edit scripts/Makefile-2.5 to add CML2 support. Look for the header
# --------- Start of config handling ---------
in particular the xconfig, menuconfig, oldconfig and config targets.
Add CML2 support there, using the separate object tree.
* Send a patch against scripts/Makefile-2.5.
Just add support for CML2 in the same style as CML1, replacing the code
in install-cml2. As a temporary measure, append '-2' to the CML2
targets so CML1 still works.
Eric, we need to send an integrated patch to Linus with both CML1
support for 2.4 parallel running and 2.5 support for the cutover. Once
the code is in 2.5, we remove the CML1 support, remove '-2' from
the CML2 targets, delete the old Makefile, Rules.make and config.in
files, delete the CML1 scripts, rename Makefile-2.5 to Makefile and
stand well back.
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/kbuild-devel
