System :: make problems



Thanks for all the help.

I have a couple things I have to do, then I'll give this a try again.  I'll let you know what happens.

To summarize 2.4 kernel compiling along with DSL procedures and your rt2500 driver:

- unpack the wanted kernel to /usr/src/linux-2.4.xx. The directory is not set in stone, it's just a habit to have 2.4 kernelsource there (which these out-of-tree drivers follow btw)
- have gcc1-with-libs and gnu-utils installed, without gcc 2.95 for gains (re-add gcc1-with-libs to overwrite it and symlink cc to gcc)
- cd there and copy the base DSL .config there from kernelsource.dsl (to the root of the unpacked linux-2.4.xx directory)
Quote
make menuconfig
make dep
make bzImage modules
sudo make modules_install
At the first step you will get to the configuration utility; you can select all parts in, out, or as a module, and get a description of each. First go to processor settings and set the cpu type to yours; this will get you the largest speed gains. Then drop a multitude of drivers not needed to save space :)

Quote
sudo cp arch/i386/boot/bzImage /boot/mykernel


Then just edit your bootloader to point to the new kernel, and your all set to reboot. If you chose grub, the file is /boot/grub/menu.lst.

After reboot you can compile the rt2500 driver (as it selects the running kernel on what to build for)

Make sure you build without SMP support, as iirc that's what causes the module to be incompatible with DSL (unless something was updated).
If you do require SMP, ndiswrapper is probably your best choice.

Oh, was this *this* driver? Then you need to build your own kernel, as DSL has only SMP ones.
OK, My first attempt at compiling the kernel was a complete failure.  I looked back at the above directions and I think I forgot to move the .config file over to the kernel root directory.  I guess that this file determines which options in 'make menuconfig' are defaulted to on or off.  I did not know what half of those options were so I just lef tthem as the default, but I noticed that most of them were defaulted to no.

I'll move the .config file over and try again.

Next Page...
original here.