Garret Crisler wrote:
After the compiler produces the managed-make-test, what operation then
produces the .elf file??
"build" compiles and links
the elf file should be visible under the "binaries" point in the project
tree. the file itself is in the "debug" subdirectory of the project.
chris
----- Original Message ----- From: "Chris Liechti" <[email protected]>
To: <[email protected]>
Sent: Tuesday, November 30, 2004 5:52 PM
Subject: Re: [Mspgcc-users] eclipse and elf file
Garret Crisler wrote:
Here is a copy of what I have in the console window.
I am using the Managed makefile.
I have the mmcu specified in both the complier and linker.
> msp430-gcc -O0 -g -Wall -mmcu=msp430x412 -mmcu=msp430x412 -o test.o
> ../test.c
something went wrong here. it should only compile. "-c" is missing here
Building target: test
msp430-gcc -mmcu=msp430x412 -o test test.o
test.o(.text+0x3a):gcrt0.S:37: multiple definition of `_unexpected_1_'
multiple definition of `InterruptVectors'
test.o prvides these symbols too, but msp430-libc provides these. so
you have it twice now.
i get this, when i create a fresh project with hardware.h and main.c
from the leds example. (eclipse 3.0.1/CDT 2.0.2)
**** Full rebuild of configuration Debug for project managed-make-test
****
make -k clean all
rm -rf main.o main.d managed-make-test
Building file: ../main.c
msp430-gcc -O0 -g3 -Wall -c -fmessage-length=0 -mmcu=msp430x1121 -o
main.o ../main.c
Finished building: ../main.c
Building target: managed-make-test
msp430-gcc -mmcu=msp430x1121 -o managed-make-test main.o
Finished building: managed-make-test
Build complete for project managed-make-test
i get the same with -mmcu=msp430x412. i'll mail you a zip with my test
project directly.
chris
