On 3 Jun 2008, at 02:35, Chris Liechti wrote:
Steven Borley schrieb:
Does anyone know which version of gcc we ought to be using
for reasonable stability but good coverage of the newer MSP430
models?
that would be 3.2.3
I've now repeated the exercise with gcc-core-3.2.3
With this version I still have no build errors compiling msp430-gcc.
Also I now have no errors with compiling msp430-libc and could use the
unmodified make file with all the targets included.
However, I now get the same errors as Jens saw when building his test
program...
$ msp430-gcc -Wall -mmcu=msp430x167 main.c
/usr/local/msp430/lib/gcc-lib/msp430/3.2.3/msp2/
libgcc.a(_copy_data.o): In function `__do_copy_data':
(.init4+0x2): undefined reference to `__data_size'
/usr/local/msp430/lib/gcc-lib/msp430/3.2.3/msp2/
libgcc.a(_copy_data.o): In function `__do_copy_data':
(.init4+0xc): undefined reference to `__data_load_start'
/usr/local/msp430/lib/gcc-lib/msp430/3.2.3/msp2/
libgcc.a(_clear_bss.o): In function `__do_clear_bss':
(.init4+0x2): undefined reference to `__bss_size'
in case of problems you might try a checkout from one month ago.
currently the HEAD is moving, preparing a new version.
Looking at CVS I see these problem symbols appeared in linbgcc.S only
about a week ago (rev 1.11). So moving back in CVS sound like a good
bet.
Thanks Chris. I'll try that next.
I'm using binutils-2.18 and It looks like these symbols ought to come
from the linker, so could this be a cause - which binutils do you all
use?
Regards,
Steven
