Hello, I am currently migrating a project from mspgcc4 to the new mspgcc toolchain. I am using the msp430-gcc (GNU GCC patched mspgcc-20110716) 4.5.3 from the official debian repositories. I am missing some hints on what changed between those versions. Here are my questions:
In our project we are using a custom linker script and we would like to keep it this way. But mspgcc will not link the executables out of the box. At first I noticed that in our linker script we had explicitly set the output architecture with OUTPUT_ARCH(msp:16) or (msp:54) which I understand is no longer supported. The linker should take the correct information from the -mmcu switch. Is this correct? And what is more of a problem: The linker won't link the default startup code like it did with mspgcc4. We are missing all of the __do_copy_data, __do_clear_bss, __do_global_ctors and __jump_to_main. Also the _reset_vector__ is not defined. When we define it in the linker script, the program will link correctly but without the default startup code. What switches are likely to cause this behaviour? Is this expected with custom linker scripts? How can we force the default startup code to be linked in? BTW this is a C++ project compiled and linked with msp430-g++. Thanks Stefan P.S. sorry if this is a double post. It seems the mailing list does not like my other mail address. ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
