Kernel build breaks
In the interests of (trying) to read my macdisk, I decided to build a
new kernel using Sid/Sarge source.
Why do computers hate me so?
Look what happened:
gcc -D__KERNEL__
-I/home/summer/kernels/kernel-image-2.4.26-i386-2.4.26/build-386/include
-Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing
-fno-common -Os -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2
-march=i386 -nostdinc -iwithprefix include -DKBUILD_BASENAME=filemap
-DEXPORT_SYMTAB -c filemap.c
filemap.c: In function `sys_sendfile64':
filemap.c:1949: Internal compiler error:
filemap.c:1949: internal error--unrecognizable insn:
(insn 358 449 367 (set (reg/v:SI 5 %edi)
(asm_operands/v ("1: movl %%eax,0(%2)
2: movl %%edx,4(%2)
3:
.section .fixup,"ax"
4: movl %3,%0
jmp 3b
.previous
.section __ex_table,"a"
.align 4
.long 1b,4b
.long 2b,4b
.previous") ("=r") 0[
(reg:DI 1 %edx)
(reg:SI 4 %esi)
(const_int -14 [0xfffffff2])
(reg/v:SI 5 %edi)
]
[
(asm_input:DI ("A"))
(asm_input:SI ("r"))
(asm_input:SI ("i"))
(asm_input:SI ("0"))
] ("filemap.c") 1947)) -1 (insn_list 333 (insn_list 357 (nil)))
(nil))
cpp0: output pipe has been closed
make[4]: *** [filemap.o] Error 1
make[4]: Leaving directory
`/home/summer/kernels/kernel-image-2.4.26-i386-2.4.26/build-386/mm'
make[3]: *** [first_rule] Error 2
make[3]: Leaving directory
`/home/summer/kernels/kernel-image-2.4.26-i386-2.4.26/build-386/mm'
make[2]: *** [_dir_mm] Error 2
make[2]: Leaving directory
`/home/summer/kernels/kernel-image-2.4.26-i386-2.4.26/build-386'
make[1]: *** [stamp-build] Error 2
make[1]: Leaving directory
`/home/summer/kernels/kernel-image-2.4.26-i386-2.4.26/build-386'
make: *** [build-stamp] Error 2
Build command 'cd kernel-image-2.4.26-i386-2.4.26 && dpkg-buildpackage
-b -uc -rfakeroot' failed.
E: Child process failed
Does anyone have any bright ideas? The visit to the site is looking more
likely:-(
--
Cheers
John
-- spambait
1aaaaaaa@computerdatasafe.com.au Z1aaaaaaa@computerdatasafe.com.au
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
Reply to: