G'day Peter,

many thanks for your reply. I've tried to leave this option out, but it 
produces a similar error:

/usr/pkg/msp430-gcc-4.4.3/bin/msp430-gcc -O2 -s -mmcu=msp430x149 -Wall 
-D__MSPGCC__  -Wl,-Map monitor.map -T msp430x149.x -o 
monitor command.o monitor.o usart.o utilities.o version.o intrjump.o iojump.o 
lowflash.o
/usr/pkg/msp430-gcc-4.4.3/lib/gcc/msp430/4.4.3/msp2/libgcc.a(_copy_data.o): In 
function `__do_copy_data':
(.init4+0x2): undefined reference to `__data_size'
/usr/pkg/msp430-gcc-4.4.3/lib/gcc/msp430/4.4.3/msp2/libgcc.a(_copy_data.o): In 
function `__do_copy_data':
(.init4+0xc): undefined reference to `__data_load_start'
/usr/pkg/msp430-gcc-4.4.3/lib/gcc/msp430/4.4.3/msp2/libgcc.a(_clear_bss.o): In 
function `__do_clear_bss':
(.init4+0x2): undefined reference to `__bss_size'
collect2: ld returned 1 exit status
gmake: *** [monitor] Error 1

The new linker script, 
/usr/pkg/msp430-gcc-4.4.3/msp430/lib/ldscripts/msp430x149.x is empty and just 
contains a header declaring 
that it is the default linker script for normal executables.

cheerio Berndt


On 18/08/10 Peter Bigot wrote:
> The -T msp430x149.x option overrides the default linker script.  Does
> the one you're using  provide definitions for those symbols?
> 
> Try eliminating that option; it shouldn't be necessary unless you're
> doing something special.
> 
> Peter
> 
> On Tue, Aug 17, 2010 at 8:54 AM, Berndt Josef Wulf <w...@ping.net.au> wrote:
> > G'day,
> >
> > Using the current SVN source tree, I've built mspgcc4 on NetBSD-5.0.2. The
> > building and installation process completed without any noticeable problems.
> >
> > When compiling projects I'm getting the following error messages:
> >
> > [...]
> > /usr/pkg/msp430-gcc-4.4.3/bin/msp430-gcc -O2 -s -mmcu=msp430x149 -Wall -
> > D__MSPGCC__  -Wl,-Map monitor.map -T msp430x149.x -o monitor command.o
> > monitor.o usart.o utilities.o version.o intrjump.o iojump.o lowflash.o
> > /usr/pkg/msp430-gcc-4.4.3/lib/gcc/msp430/4.4.3/msp2/libgcc.a(_copy_data.o): 
> > In
> > function `__do_copy_data':
> > (.init4+0x2): undefined reference to `__data_size'
> > /usr/pkg/msp430-gcc-4.4.3/lib/gcc/msp430/4.4.3/msp2/libgcc.a(_copy_data.o): 
> > In
> > function `__do_copy_data':
> > (.init4+0xc): undefined reference to `__data_load_start'
> > /usr/pkg/msp430-gcc-4.4.3/lib/gcc/msp430/4.4.3/msp2/libgcc.a(_clear_bss.o): 
> > In
> > function `__do_clear_bss':
> > (.init4+0x2): undefined reference to `__bss_size'
> > collect2: ld returned 1 exit status
> > gmake: *** [monitor] Error 1
> >
> > This application compiled fine with an older version of MSPGCC  (gcc-3.3.2 
> > by
> > memory).
> >
> > I've searched the mailing list archive and found a similar case in 2008 on 
> > OSX
> > and the solution was the application of the binutils patches. However, all
> > patches have been applied to the source tree.
> >
> > MSPGCC was build using the "buildgcc.sh" script with the options gcc-4.4.3,
> > gdb-7.0.1, libc-20100430 and stripped executables.
> >
> > The Makefile contains the following configuration lines:
> >
> > CPU     = msp430x149
> > CC      = /usr/pkg/msp430-gcc-4.4.3/bin/msp430-gcc
> > LD      = /usr/pkg/msp430-gcc-4.4.3/bin/msp430-ld
> > OBJCOPY = /usr/pkg/msp430-gcc-4.4.3/bin/msp430-objcopy
> > OBJDUMP = /usr/pkg/msp430-gcc-4.4.3/bin/msp430-objdump
> > CFLAGS  += -O2 -s -mmcu=${CPU} -Wall -D__MSPGCC__
> >
> > Has anyone else seen this and if so, what was the solution?
> >
> > With many thanks in advance,
> >
> > cheerio Berndt
> >
> > ------------------------------------------------------------------------------
> > This SF.net email is sponsored by
> >
> > Make an app they can't live without
> > Enter the BlackBerry Developer Challenge
> > http://p.sf.net/sfu/RIM-dev2dev
> > _______________________________________________
> > Mspgcc-users mailing list
> > Mspgcc-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/mspgcc-users
> >
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
> 
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Mspgcc-users mailing list
> Mspgcc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
> 

Reply via email to