Re: newlib does not pick up the right cross-compiling gcc

[Josef Wolf <jw at raven dot inka dot de>]

On Sat, Feb 06, 2010 at 09:11:15PM +0100, Josef Wolf wrote:
> Without the --enable-targets option, I can build the current versions of the
> toolchain: binutils-2.20, gcc-4.4.3 and newlib-1.18.0. I have not checked
> (yet) whether the code that this toolchain generates actually works, though.

I've checked now, and see it failing. Looks like the linker fetches wrong
version of the newlib (coldfire, maybe?)

I see this code for the strchr() function in my emulator:

 link.w a6,#$0
 movem.l d2-d4,-(a7)
 move.l ($c,a6),d1
 move.l ($8,a6),d0
 move.b d1,d2
 beq.w $35040
 dc.w $e8c0               ; this line crashes the processor
 bclr d3,d2
 [ ... ]

when I compile newlib with binutils-2.16, and gcc-3.3.6 and my own stuff
with binutils-2.20 and gcc-4.4.3, everything seems to work.

This is how I compile:

 m68k-unknown-elf-gcc -ansi -pedantic -Wall -Wcast-align -Wstrict-prototypes \
    -Wmissing-prototypes -std=c89 -O2 -m68332 -msoft-float -c -o main.o main.c
 m68k-unknown-elf-gcc -nostartfiles -Wl,--cref -Wl,-Ttext=0,--entry=entry \
    -Wl,--oformat,elf32-m68k -Wl,--cref,-Map,bestd.gmap \
    -Wl,-T,ldscript -ansi -pedantic -Wall -Wcast-align \
    -Wstrict-prototypes -Wmissing-prototypes -std=c89   -O2  -m68332 \
    -msoft-float  -o bestd.gelf main.o -lc

Any ideas?