MVME2306 : kernel 2.2.6 SUCCESS !
paubert at iram.es
Thu Apr 22 02:30:56 EST 1999
On Wed, 21 Apr 1999, Simone Piccardi wrote:
> I just finished to try this procedure (with some more step added) to
> cross-compile the kernel on my PC, but it does not work.
> I did all the step up to the distclean, then I modify the Makefile
> (according to Matt Porter instructions), I copied the
> mvme2600.config.nfsroot as .config and did make oldconfig.
> Everything up to here went fine, without any error or warning.
> Then I did make dep and make clean (always using the Matt Porter
> instruction) and the make zImage, at the end the error was this:
> powerpc-linux-gcc -D__KERNEL__ -I/home/ppc/linux/include -Wall
> -Wstrict-prototypes -O2 -fomit-frame-pointer -D__powerpc__ -fsigned-char
> -msoft-float -pipe -fno-builtin -ffixed-r2 -Wno-uninitialized -mmultiple
> -mstring -mcpu=603e -D__powerpc__ -msoft-float -pipe -fno-builtin -Wall
> -mmultiple -mstring -I../boot -I/home/ppc/linux -D__KERNEL__ -O2
> -fomit-frame-pointer -mrelocatable -ffixed-r13 -D__BOOT__ -DDEBUG -c -o
> zlib.o zlib.c
> zlib.c:83: string.h: No such file or directory
> zlib.c: In function `inflate_blocks':
> zlib.c:878: warning: implicit declaration of function `memcpy'
> make: *** [zlib.o] Error 1
> make: Leaving directory `/home/ppc/linux/arch/ppc/prepboot'
> make: *** [zImage] Error 2
> I'm a little bit worried about the -mcpu=603e switch but I don't think
> this can be relate to the error.
No, it does not. It is just an optimization because I happen to have 603e
and the default scheduling is bad on it (it tends to expand multiplies to
series of shift and add since it believes that multiplication is much more
expensive than it actually is on most PPC processors). Scheduling on 750
is probably different but this should not have any major adverse
However this problem is obviously my fault, I did not track some changes
:-( You should include linux/string.h instead of string.h.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
More information about the Linuxppc-dev