SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a question that I can't for the life of me find the answer to after searching all around the net, and I have no place else to turn.
My problem is this, I decided to give the new 2.6-test5 a go after using the default slack9 kernel since installation. I've built kernels before, and looked at many different sites on how to build the 2.6 series, but I think my problem is unexplainable.
When I get to the "make bzImage" step, the compile(with gcc 3.2.2 that comes with slack9) will invariable die at some .c file. The thing is, if I clean the make process, and redo everything, the process will die at an entirely different .c file. Each time I clean and retry, bam, another error at a different step. I have used the same config file, and using a default one. No luck, same thing.
The only thing I can think of is that my computer has some bad ram or the HD is messed up, but I've had no problems with it before. I've used mandrake, windows xp, gentoo, and slackware, and had nothing of the sort like this happen before.
I've compiled and built many other large programs(not quite as large as a kernel) with no problems at all. I don't get whats happening. Other people have had no problems compiling their kernels with the same setup, so my question is this: what gives?
Any, and I mean any, help would be greatly appreciated. My laptop is somewhat slow with the GUI, so the added speed would be much needed.
Are you doing the make mrproper prior to doing the configure? I know the first kernel compile I did I inadvertently skipped this step and had some similar problems. Are you following the Kernel Compile HOWTO?
I did follow the howto, and I did do the mrproper step. I've compiled kernels before, but this is just an oddball problem. As we speak, my laptop is furiously compiling 2.4.22 as per Modorfs suggestion. If it succeeds, I'll be sure to let you guys know. If it fails, then I'm clueless. Hopefully it succeeds and I can get working on 2.6.
If I get past the 2.4.22 build ok, then I'll try and post some of my error messages I get.
the -bk that UnTamed referred to is a set of patches. You might also try the -ac line of patches, I've had good luck with the -ac patches. However considering it happens with both 2.4.22 and the 2.6.x kernels if I was you I would try to compile one of the old sources you previously compiled successfully to see if that works. Because if it doesn't it's probably not the new kernels.
I had faced this similar problem before. Build the kernel half way and encounter a gcc error.
However, (after some trial and error), I notice the problem seems to be related to hardware rather than software. Is your CPU overclocked? Or is your CPU overheated? You can try copy the same .config file and build it at antther system. After built, copy the bzImage to the target machine (remember to include the modules as well).
This is a work around that I can think of at the moment.
Built 2.6-test* kernel is easy, just make sure you have downloaded the new kernel module-init-toolsl from: