Re: [kbuild-devel] Converting the 2.5 kernel to kbuild 2.5

It's not the CML1 language spec that interests me, just the user interface.  All
I care about is being able to do make menuconfig and make oldconfig, and get the
same results as before.  What goes on "under the surface" doesn't interest me at
all.

In fact, here's all I want to know about the whole CML2/kbuild 2.5 issue.  Right
now I upgrade my kernel like this (simplified slightly):

<apply latest patches>
mv .config ..
make mrproper
mv ../.config .
make oldconfig
make dep
make bzlilo modules modules_install
<reboot>

Will I still be able to do it this simply in 2.5.x?  (Assuming there's
eventually a 2.5.x I can get to compile cleanly.  :-)

Wayne

John Stoffel <[e-mail]> on 12/04/2001 10:31:10 AM

To:   Christoph Hellwig <[e-mail]>
cc:   Keith Owens <[e-mail]>, [e-mail],
      [e-mail], [e-mail] (bcc: Wayne
      Brown/Corporate/Altec)

Subject:  Re: [kbuild-devel] Converting the 2.5 kernel to kbuild 2.5

Christoph> I still strongly object to it and I know lots of kernel
Christoph> hackers are the same opinion.

I'm not a hacker, but I think it's a good thing to move to CML2.  I've
tested it and it's got some nice features.  The Python issue I don't
think is too onerous to require of people.  And wasn't there someone
out there porting CML2 to straight C code?

Why are people so wedded to the CML1 language spec anyway?

John
   John Stoffel - Senior Unix Systems Administrator - Lucent Technologies
      [e-mail] - http://www.lucent.com - 978-952-7548