View Single Post
Old 23rd May 2007, 20:06
modul8r modul8r is offline
Junior Member
Join Date: May 2007
Posts: 10
Thanks: 4
Thanked 0 Times in 0 Posts

I tried both suggestions but neither are helping.

1. Regarding the suggestion to modify the checksum.h file, I did that and got further. I then had to also modify a floppy.h file the same way. Again, I got further until I ended up with a different error:

/usr/bin/make -C ide
make[3]: Entering directory `/usr/src/linux/drivers/ide'
/usr/bin/make all_targets
make[4]: Entering directory `/usr/src/linux/drivers/ide'
ld -m elf_i386 -r -o ide-mod.o ide.o ide-features.o cmd640.o ide-adma.o ide-dma.o ide-pci.o piix.o rz1000.o ide-proc.o
ld -m elf_i386 -r -o ide-probe-mod.o ide-probe.o ide-geometry.o
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -c -o ide-cd.o ide-cd.c
In file included from ide-cd.c:318:
ide-cd.h:438: error: long, short, signed or unsigned used invalidly for `slot_tablelen'
make[4]: *** [ide-cd.o] Error 1
make[4]: Leaving directory `/usr/src/linux/drivers/ide'
make[3]: *** [first_rule] Error 2
make[3]: Leaving directory `/usr/src/linux/drivers/ide'
make[2]: *** [_subdir_ide] Error 2
make[2]: Leaving directory `/usr/src/linux/drivers'
make[1]: *** [_dir_drivers] Error 2
make[1]: Leaving directory `/usr/src/linux'
make: *** [debian/stamp-build-kernel] Error 2

Not sure how to proceed here, as far as this "manually modify the files" route is concerned.

For what it's worth, here's the section in ide-cd.h that it's referring to:

#if defined(__BIG_ENDIAN_BITFIELD)
__u8 mech_state : 3;
__u8 door_open : 1;
__u8 reserved1 : 4;
__u8 reserved1 : 4;
__u8 door_open : 1;
__u8 mech_state : 3;
#error "Please fix <asm/byteorder.h>"

byte curlba[3];
byte nslots;
__u8 short slot_tablelen;

2. It seems that using an older version of GCC would be easier, but I don't understand exactly how to do so. The suggestions on that mailing list aren't specific enough for a novice such as myself.

First example: "I think prepending "CC=gcc-2.95" to the command line ought to be enough."

Second example: "make bzImage CC=gcc-2.95"

Examples of syntax? I don't understand.

How exactly do I incorporate "use old GCC 2.95" with my command that's giving problems (fakeroot make-kpkg --revision=custom.1.0 kernel_image)?

Thanks again for all of your help. I appreciate it very much.
Reply With Quote