Thank you Tom,

That was the kind of answer that I hoped for.
I just took a quick look at the README file,
and cut out all the many words. I then made
a file from where I copied the lines by using
my mouse. I did not dare to include the "make install".
Yes, you are right. The number of lines can be cut
down to about half.

I have installed the new gcc-3.1 compiler as the default
gcc without too many difficulties. I have now compiled
the 2.4.18-16 enterprise kernel minus SMP, and for
Pentium4. I used "make menuconfig" as "make xconfig"
seems to be broken (see below). Maybe I should have
updated some other package. Anyway, the compile proceeded
without any problems.

I am not sure, however, that any specific P4 code was
generated. Here is my shorter recipe:

Procedure for compiling the kernel:

(1) cd /usr/src/linux
(2) "make mrproper" in case we start from scratch.
(3) cp /boot/config-2.4.18-16mdkenterprise /usr/src/linux/.config
(4) edit .config followed by "make oldconfig" or "make menuconfig"
(5) "EXTRAVERSION = -16P4" in /usr/src/linux/Makefile
(6) "export INSTALL_PATH=/boot" in /usr/src/linux/Makefile
(7) "make dep && make bzImage && make modules"
(8) "make modules_install && make install"
(9) inspect /boot and /etc/lilo.conf, and run lilo (to be sure).

"make xconfig":
cat header.tk >> ./kconfig.tk
./tkparse < ../arch/i386/config.in >> kconfig.tk
3rdparty/dxr3/Config.in: 8: can't handle dep_bool/dep_mbool/dep_tristate
condition
make[1]: *** [kconfig.tk] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.18-16mdk/scripts'
make: *** [xconfig] Error 2



On Thu, 2002-05-09 at 21:32, Tom Brinkman wrote:
> On Thursday 09 May 2002 12:04 pm, Bjarne Thomsen wrote:
> 
> > But I have not tried to compile 2.4.18-6mdk using the
> > default gcc-2.96.
> 
>    I have, and also including -12 and -13mdk using gcc-2.96
> -13 was to have some big improvement, but i forget what it was ;>
> 
> > I edited the EXTRAVERSION  [Makefile]  variable,
> > so my own kernel can live without interfering with
> > the standard kernels.
> 
>     You didn't go far enough, and then again too far.  Best kernel 
> install/upgrade guidelines are at mandrakeuser, IMO.  
> 
> > Here are my 19 points:
> 
>    Way too many partner ;)
> >
> > Procedure for compiling the kernel.
> >
> > ( 1) cd /usr/src/linux
> > ( 2) "make mrproper"
> > ( 3) cp /boot/config /usr/src/linux/.config
> 
>   in my last compile, I used   cp /boot/config-2.4.18-13mdk .config   
> 'Course as you properly point out, this needs to be after mrproper.  
> I'd like if y'all would check the cooker ML archive for the reasons/ 
> discussion on why mrproper is still 'the way to go'/necessary with 
> ML kernels.  To satisfy yourself, or explain it better to me ;)
> 
> > ( 4) edit .config           if necessary.
> 
>    I do, but only to set K7 as the arch. I have an oc'd 1.4 Tbird 
> with VIA chipset, compiling for K7 seems to provide slight benefits, 
> including stability.  Strictly anecdotal, maybe just psychological ;)
>   
> > ( 5) Alternate configuration commands:
> >      (a) "make config"      to configure the basic kernel.
> >      (b) "make menuconfig"  Text based color menus, radiolists &
> > dialogs.
> >      (c) "make xconfig"     X windows based configuration tool.
> >      (d) "make oldconfig"   Default all questions based on the
> > contents of
> 
>    I use oldconfig, to make a default 'Mandrake' kernel, with just my 
> edit to k7 arch.  I know it says not to, ie, " # Automatically 
> generated make config: don't edit", but I've never had a problem doin 
> so ;)
> 
> >                             your existing ./.config file.
> > ( 6) edit "EXTRAVERSION = -14mdkbt" in /usr/src/linux/Makefile
> 
>     I would just edit this to -14k7 in my situation.  Here's where I 
> believe you don't go far enough.  Also enable (uncomment the line) 
> further down,      export  INSTALL_PATH=/boot     
> 
> > ( 7) "make dep"             to set up all the dependencies
> > correctly. ( 8) "make bzImage"         to create a compressed
> > kernel image. ( 9) "make modules"         to compile the modules.
> 
>     Now here's (IMO) where you get out of order/include unnecessary 
> steps.  As MU advises,
>    make dep && make clean && make bzImage && make modules
>        followed with,
>    make modules_install && make install
> 
>     The 'make install' will take care of all the cp'ing, linking, and 
> mkinitrd'ing, etc. (you get into), edit lilo.conf, and run it for 
> you.  Less chance for user error, IME  ;)  Still, bein an untrusting 
> soul, I usually cd to /boot and run 'll' to make sure the pointers 
> were created to the new kernel. Then cd to /etc, do a 'less' on 
> lilo.conf to make sure the new kernel is an option, then run 'lilo', 
> just to make sure there's no error msg's. Rarely has been, good job 
> Mandrake!  ;)
> 
> > (10) "make modules_install" to install the modules in /lib/modules/
> > (11) cp /usr/src/linux/arch/i386/boot/bzImage
> > /boot/vmlinuz-2.4.18-14mdkbt
> > (12) cp /usr/src/linux/System.map /boot/System.map-2.4.18-14mdkbt
> > (13) cp /usr/src/linux/.config /boot/config-2.4.18-14mdkbt
> > (14) cd /boot
> > (15) ln -sf System.map-2.4.18-14mdkbt System.map
> > (16) ln -sf config-2.4.18-14mdkbt config
> > (17) mkinitrd -v /boot/initrd-2.4.18-14mdkbt.img 2.4.18-14mdkbt
> > (18) edit lilo.conf:
> >      image = /boot/vmlinuz-2.4.18-14mdkbt
> >      label = 2418-14bt
> >      initrd = /boot/initrd-2.4.18-14mdkbt.img
> > (19) Type lilo
> 
>   11 -> 19 are unneeded, only present more chance for user error ;p
> 
>     As a footnote, I don't recommend usin newer kernels unless you 
> also either monitor the cooker ML, or at least check it's recent 
> archive. OTOH, newer cooker kernels are usually much better than the 
> kernels shipped with 'release' versions, specially ML8.2, and 
> specially tryin to use vanilla source from kernel.org.  I suspect 
> this is for compatibility over a wide range of hardware, 
> configurations, and users.  YMMV ;)
> 
>      Also, from lurking on the cooker list, compiling the latest 
> kernels with <= gcc 3.04 seems to be an expected problem.  I didn't 
> have any usin ML8.2's gcc 2.96.   Please don't take any of my above 
> comments as criticism, only meant as fodder for discussion
> 
> tom/$ uname -r
> 2.4.18-13k7
> 
> tom/$ gcc -v
> Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux-gnu/2.96/specs
> gcc version 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk)
>   
> -- 
>     Tom Brinkman                    Corpus Christi, Texas
> 
> ----
> 

> Want to buy your Pack or Services from MandrakeSoft? 
> Go to http://www.mandrakestore.com



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to