LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   kernel compile error (https://www.linuxquestions.org/questions/slackware-14/kernel-compile-error-694241/)

seaelf 01-01-2009 08:26 AM

kernel compile error
 
hi and happy new year
I am using Slack 12.0 with the 2.6.21.5 kernel. I was hoping to try 2.6.5 and followed the instructions in the Kernel Compile Guide listed here in the Slack forum as well as in Shilos page. I've compiled 2.4's without a hitch but this time I am not sure what to do. Searching hasn't helped, I don't seem to see the same error message posted.

After extracting 2.6.5 in /usr/src I removed the old Linux link and made a new link to 2.6.5 and then renamed it linux. Then I cd'd to /usr/src/linux and typed 'make menuconfig'. This is what I get:

bash-3.1# make menuconfig
HOSTCC scripts/kconfig/mconf.o
scripts/kconfig/mconf.c:91: error: static declaration of 'current_menu'
follows non-static declaration
scripts/kconfig/lkc.h:63: error: previous declaration of 'current_menu'
was here
make[1]: *** [scripts/kconfig/mconf.o] Error 1
make: *** [menuconfig] Error 2

Any suggestions or sites would be great.
Thanks

Didier Spaier 01-01-2009 08:49 AM

As a rule of thumb, compiling an *older* kernel than the one shipped with the distro is *not* recommended. You can find incompatibility issues with gcc's version used, and may be with kernel headers.

May be I'm too curious, but why do you need an older kernel ?

seaelf 01-01-2009 09:19 AM

Didier-
Thanks for the reply. I think I had better check the kernel info because I thought the 2.6.5 was newer then the 2.6.21.5. I don't want to compile an older kernel.
This is not a good way to start 2009!
all the best
Neil

seaelf 01-01-2009 09:25 AM

Didier and the rest of the group-
I apologize for being so stupid. Didier, thanks for bringing the kernel info to my attention....2.6.5 is not what I should have downloaded.
Sorry to have taken up space. I am looking forward to trying it again...
Neil

Didier Spaier 01-01-2009 10:15 AM

Neil, don't be sorry, it can happen to everybody -- including me, of course ;)

I wish you and all readers a very happy new year.

Brett Delport 01-23-2009 07:50 AM

Same problem
 
Hi all

I am having the same problem (exactly) that is reported here. I am using slackware 12.0, and am looking to install and older kernal than the one it shipped with. (ships with 2.6.21.5) and we want to change it to 2.6.8.1. We are having a problem running some older hardware on the newer kernal. As far as I have seen, the hardware is compatible with 2.6.8.1. It is a parallel port data logger (picologger). We use this hardware for scientific experiments on Antarctica, and as i am currently in Antarctica with this problem, its the best solution I can think of. Could anyone help me resolve this problem, or is it just impossible to install such old kernals on newer releases of slackware?

Thanks in advance for the help :)

Brett

Alien Bob 01-23-2009 08:14 AM

Quote:

Originally Posted by Brett Delport (Post 3418549)
Hi all

I am having the same problem (exactly) that is reported here. I am using slackware 12.0, and am looking to install and older kernal than the one it shipped with. (ships with 2.6.21.5) and we want to change it to 2.6.8.1. We are having a problem running some older hardware on the newer kernal. As far as I have seen, the hardware is compatible with 2.6.8.1. It is a parallel port data logger (picologger). We use this hardware for scientific experiments on Antarctica, and as i am currently in Antarctica with this problem, its the best solution I can think of. Could anyone help me resolve this problem, or is it just impossible to install such old kernals on newer releases of slackware?

Thanks in advance for the help :)

Brett

I checked google and I found reports that 2.6.8 will not properly compile with the gcc4 compiler (Slackware 12.0 has gcc 4.1.2).
On the other hand, I found another message which suggested to edit the file /path/to/your/linux-2.6.8.1/scripts/kconfig/mconf.c and replace all occurrences of "current_menu" with "cur_menu".
Then start the kernel compilation again. Worth a try, but I give you a slim chance of success.

Downgrading gcc is not an option either because that is not the only thing you'll have to change then. It would be wiser to downgrade Slackware to an earlier release in that case.

Your message states that this piece of hardware is compatible with 2.6.8.1 - does that mean you have a binary kernel module for that kernel and no sources? Doesn't the vendor have other kernel modules too?

Eric


All times are GMT -5. The time now is 03:44 PM.