Re: [arm-gnu] Pb compiling u-boot

[Paul Brook <paul@xxxxxxxxxxxxxxxx>]

On Monday 18 July 2005 16:02, Dupas.External@xxxxxxxxxxxx wrote:
> `/home/dupas/linux/sources_u-boot/u-boot-1.1.2/examples'
> /home/dupas/linux/tool-chain/bin/arm-none-linux-gnueabi-gcc -g  -Os
> -fno-strict-aliasing  -fno-common -ffixed-r8 -mshort-load-bytes
> -msoft-float -D__KERNEL__ -DTEXT_BASE=0x01000000
> -I/home/dupas/linux/sources_u-boot/u-boot-1.1.2/include -fno-builtin
> -ffreestanding -nostdinc -isystem
> /home/dupas/linux/tool-chain/bin/../lib/gcc/arm-none-linux-gnueabi/3.4.3
> /include -pipe  -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -Wall
> -Wstrict-prototypes -c -o stubs.o stubs.c

> cc1: error: invalid option `short-load-bytes'

This option is no longer supported. It is only meaningful on very old 
(pre-armv4) chips that do not have load-halfword instructions.

> cc1: error: invalid option `apcs-32'

This option is no longer supported. gcc no longer supports 26-bit mode. The 
default behaviour is to generate 32-bit mode code. Again this only matters on 
very old CPUs.

> stubs.c:1: warning: target CPU does not support interworking

The ARM EABI requires code be interworking safe. This is not possible on armv4 
CPUs, hence the warning. If your CPU is thumb capable you may wish to use 
armv4t instead.

> what shall I do?

Fix your build system to not use the old commandline options.

Paul

P.S. Note that some versions of u-boot incorrectly use local register asm 
variables, and may be miscompiled. I don't know if this has been fixed in 
recent releases.