Hello all,

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.

Thanks everyone,
-Flecko

What about getting 2.4.22 (current stable) and compiling that, see if you get the same kind of errors. There might be a bug in the current test kernel that you just stumbled on.

The other thing I can suggest is posting some of the compile time errors you are getting to this forum and the kernel developmen forum.

Yeah, maybe if you can remember some of the different .c files that caused the compilation to stop and post them here, that would be useful too.

-zsejk

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?

slight

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.

Thanks everyone,
-Flecko

Not good...while doing a "make zImage" on the 2.4.22 source...I get this...

memory.c: In function `do_wp_page':
memory.c:1004: internal error: Illegal instruction
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[2]: *** [memory.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4.22/mm'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.22/mm'
make: *** [_dir_mm] Error 2
bash-2.05b#


Anyone have any ideas? I'm gonna try cleaning and then doing a "make bzImage" for the time being...see what that does.

-Flecko

Ok...not good...after restarting the whole process, I got another error while doing the "make bzImage" step...

floppy.c: In function `redo_fd_request':
floppy.c:2985: internal error: Illegal instruction
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[3]: *** [floppy.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.22/drivers/block'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.22/drivers/block'
make[1]: *** [_subdir_block] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.22/drivers'
make: *** [_dir_drivers] Error 2
bash-2.05b#

I'm stumped. Should I change gcc versions? This is really bugging me.

Thanks to everyone again,
-Flecko

Try to patch to the latest -bk,
...and it might be a good idea to use "make" [...as suggested when your config is saved] instead of "make bzImage" and "make modules".

patch to the latest what? and I'll try just "make" in a few minutes....

-Flecko

just doing "make" caused yet another error in serial.c...

I'm totally clueless...I'm gonna reboot, and try building without being under X.

-Flecko

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.

Suggestion :: Do an MD5 verifictation of the source tar for linux-2.4.22

how much free space do you have, hard drive and ram? serious question.

Adding anything unusual to your kernel config (not sure how to clarify that further than post your .config file).

Something that would probably be completely annoying to do, but...



... perhaps you can try installing the latest stable gcc version, and then compile the newest kernel with that?

ftp://ftp.gnu.org/pub/gnu/gcc/gcc-3.3.1.tar.gz

-zsejk

Har...I dunno how or why, but getting the gcc version from slackware-current did the trick.

I would have never guessed it, but I'm in bizness. I'm building 2.6-test5 as we speak. Thanks everyone for putting up with me.

Note to other Toshiba 1625CDT users, compile the kernel with gcc3.2.3 or else =P

Thanks again!,
-Flecko

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:

http://www.kernel.org/pub/linux/kern...rusty/modules/

Type make after the finish configure the kernel.

Refer to the kernel source Documentation/CHANGES files for details of dependancy to use 2.6-test kernel.

NOTE: 2.6.x compiling is a bit different from 2.4.x, so no all the steps for 2.4.x is same as 2.6.x

Hope this help...