From: Jeff T. <jw...@me...> - 2001-02-08 16:46:11
|
I recently placed this as a comment to the cvs source being available on sourceforge but figured this would be a more appropriate place to put my questions. First a note about my setup RedHat 6.2 binutils-sh4-linux-010127-2.i386.rpm gcc-sh4-linux-2.97.001120-3.i386.rpm gdb-sh-linux-5.0.001127-2.i386.rpm Please note that the gcc is actually -2.deb version, but alien increased the number when I converted it. I was unable to find the -1 version as listed in the HOWTO document. When I compile the firstkernel tarball's source I get the following error: make[1]: Entering directory `/root/box/kernel/arch/sh/kernel' sh4-linux-gcc -D__ASSEMBLY__ -D__KERNEL__ -I/root/box/kernel/include -ml -m4-nofpu -c -o entry.o entry.S entry.S: Assembler messages: entry.S:375: Error: must be @(r0,...) entry.S:376: Error: must be @(r0,...) entry.S:377: Error: must be @(r0,...) entry.S:378: Error: must be @(r0,...) entry.S:379: Error: must be @(r0,...) entry.S:433: Error: must be @(r0,...) make[1]: *** [entry.o] Error 1 make[1]: Leaving directory `/root/box/kernel/arch/sh/kernel' make: *** [_dir_arch/sh/kernel] Error 2 I assume that this is caused by the problems with different gcc versions as mentioned in the HOWTO document. Has anyone else got this going with this version of gcc from m17n.com? I also retrieved the cvs source and attempted to compile. In this case I get a failure in the make dep: make[4]: Leaving directory `/root/box/linux/net/bridge' make -C core fastdep make: Entering an unknown directory make: *** core: No such file or directory. Stop. make: Leaving an unknown directory make[3]: *** [_sfdep_core] Error 2 make[3]: Leaving directory `/root/box/linux/net' make[2]: *** [fastdep] Error 2 make[2]: Leaving directory `/root/box/linux/net' make[1]: *** [_sfdep_net] Error 2 make[1]: Leaving directory `/root/box/linux' make: *** [dep-files] Error 2 Also when I do a make vmlinux not suprisingly I get a: [root@c895938-a linux]# make vmlinux sh4-linux-gcc -D__KERNEL__ -I/root/box/linux/include -Wall -Wstrict-prototypes -O1 -g -m3 -pipe -c -o init/main.o init/main.c In file included from /root/box/linux/include/linux/capability.h:17, from /root/box/linux/include/linux/binfmts.h:4, from /root/box/linux/include/linux/sched.h:8, from /root/box/linux/include/linux/mm.h:3, from /root/box/linux/include/linux/slab.h:13, from /root/box/linux/include/linux/malloc.h:3, from /root/box/linux/include/linux/proc_fs.h:4, from init/main.c:14: /root/box/linux/include/linux/fs.h:286:28: linux/shmem_fs.h: No such file or directory /root/box/linux/include/linux/fs.h:447: field `shmem_i' has incomplete type /root/box/linux/include/linux/fs.h:699: field `shmem_sb' has incomplete type In file included from /root/box/linux/include/linux/mm.h:4, etc..etc.. So, the next question is, has anyone had any luck in building these sources? Any tips or thoughts are welcome! I'll be spending some time this weekend working on these problems and trying to get things going. I work for a OS level computer security company and have two other kernel developers who are going to be getting linux going on their systems (we want to get our security extensions on the dreamcast just for fun!), so hopefully we'll be able to make a few substantial contributions to the effort. Thanks for any help! Jeff Jeff Thompson Software Evangelist and Visionary Senior Security Analyst Argus Systems Group, Inc. |