Problems compiling 2.4.20
Anyone having problems compiling or recompiling
the 2.4.20 kernel in Slackware 9.0? I can't even get past 'make dep' which is usually "warning" and "error" free. I will not post all of the problems but will say that ususlly these problems result from having an incomplete d/ portion of the distro installed. I can assure you this is not the case here. The kernel sources were not part of the original install since they would not fit on the CD, but they were downloaded and instslled separately with no problems. I don't see any kernel patches in the distribution tree. Help, please! TIA |
Did you run make config first?
Do you have a working gcc? Do you have depmod installed? Do you have a working bin86? |
Hmmmm?
depmod? Is this part of the d/ portion of the install tree? I don't see it in either 9.0 or 8.1. Pkgtool doesn't show it installed under either. Kernel recompiles nicely w/o this package on 8.1. Maybe it's a setting of some kind; in the Makefile? I'm at a loss. |
I don't know what this d/ thing is you're talking about. Maybe you could use it's real name?
|
It's hard to say... you've been a bit vague. What are the errors? What do the errors pertain to exactly? Missing files? Syntax errors? What?
btw, to the other poster, he's talking about the 'd' series of the install archives. -VonZippa |
Depmod is part of the modutils package in /slackware/a, have you followed the kernel compile guide sticky at the top of this forum?
And posting error messages will help us to pinpoint the problem. |
Not sure I understand why;
I rebooted to a different OS to perform some other functions and the rebooted into Linux 9.0. In order to get a list of warnings and errors, I re-ran 'make dep' and to my amazement, no errors. I continued with the rest of the makes, copied the bzImage to boot, reconfigured LILO and rebooted. The new kernel booted properly; everything seems to be OK. I'll let you know. The reason I recompiled was to create a patched kernel that would run win4lin. I'll see if I can install it under this new kernel. Thanks for your help! One final thing; I usually run the makes with '> dump'. so that all that appears on the screen are actual warnings and errors. However I don't know how to capture these messages into a file so I can keep a sort of permanent record. If anyone knows how to do this, I'd appreciate an example. |
On your output command at the end try using "1>output.dump 2>output.errors"
I believe the numbers are the file handles and they are 0-stdin, 1-stdout, 2-stderr. The text part is just the filename or device desired. |
I may have spoken too soon.
When I tried to install win4lin under the newly compiled kernel, I gat the error message that the kernel was not win4lin enabled. So, it didn't work. Went back, redid the configuration (make menuconfig) and completed the various make steps. I got the warnings again on the 'make dep" step, but these were apparently not so significant as to prevent the rest of the compile. I got a few warnings on the bzImage compile but I always do so no worries. Completed the compile and re-ran the win4lin setup. Hooray! Now it works. I suppose there are going to be some oddities when using a new compiler (gcc 3.2.2). Oddly enough, the kernel source Documentation says that gcc 2.95.3 is recommended, well maybe just the earliest version you can use. I can remember when it was recommended that only 'egcs' be used to compile a kernel. BTW: Thanks for the tip on isolating errors to a file. I knew it was something simple like that. I have never really understood stdout, stderr. Thanks again! |
All times are GMT -5. The time now is 02:36 PM. |