> -----Original Message----- > From: Matthias Hartmann [mailto:matthiashart...@versanet.de] > Sent: Monday, September 19, 2011 14:13 > To: mspgcc-users@lists.sourceforge.net > Subject: Re: [Mspgcc-users] memory.x not found and debugger crashing > > To be more specific: > > set CFLAGS=-g -Os -mmcu=msp430f1611 > > msp430-gcc -c %CFLAGS% -o build\main.o main.c > > msp430-gcc -c %CFLAGS% -o build\xluper430430.o xluper430430.c > > msp430-gcc -c %CFLAGS% -o build\xluper430430testencodings.o > xluper430430testencodings.c > > msp430-gcc %CFLAGS% -Wl,-Map,build\x4.map build\main.o > build\xluper430430.o build\xluper430430testencodings.o -o > build\x4.firmware
Oh, that's interesting. You are saying that one needs to invoke the linker through the compiler rather than invoking it directly? Thanks a lot Alessandro ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
