Hi

This is my first kernel compile attempt.

I have tried to follow all messages here on Linuxquestions for compiling 2.6.0 and 2.6.1 using a working Slackware 9.1 (bare.i) installation without X/Gnome/KDE. But, it just gives me a long suite of error messages.

Everything works fine up till "make mrproper"

then, when I type "make menuconfig" or "make config" I just get those error messages.

They are too many so I can't see the beginning, but the end with error messages. (Should I increase the buffer and how do I do that? BTW)

Example of the last two error messages:

make[1] : *** [scripts/fixdep] Error1
make : *** [scripts/fixdep] Error2

I use the included gcc 3.2.3. It's a dedicated machine for learning to compile the kernel (Pentium 120 MHz, 32 MB RAM etc) so I have nothing valuable here.

Thanks for any help

hi and welcome Fr33B33R,
did you try to put the output to a file?
if you don't access the "blue screen" of the menuconfig, you can do the following..
make menuconfig > test
in this case, i think this will work...
then please, post the file test here...
Regards,
Slackie

Hi

Thanks for your reply

The only thing contained there is:

"HOSTCC scripts/fixdep"

without the quotation marks

do you have glibc installed?

the fact that slack 9.1 doesnt include that by default has cost me many hours (twice)

i forgot about glibc the last time i did a clean install, then tried to compile 2.6.0, and i had errors similar to yours.

at least the errors you get when compiling 2.4.* made a bit more sense :-/

Hi

Well, I suppose I did have glibc as I have compiled using g77 (which I believe uses glibc).

Anyhow, I re-installed the old Slackware and made sure glibc was there in place. And, voilá, it worked! Thanks!

But, now I get a warning when using 2.6.1:

FATAL: could not load /lib/modules/2.6.1/modules.dep : No such file or directory
FATAL: could not load /lib/modules/2.6.1/modules.dep : No such file or directory

(repeated twice)


Is this as fatal as the name implies? IIRC, I compiled using the new loadable/unloadable modules option. Could that be the issue?