Re: [Mspgcc-users] Notice of elimination of genericized mcu names in uniarch

2010-12-23 Thread Peter Bigot
That is certainly a good goal and I'd like it to be reachable, but whether it can be done depends on how many assumptions you want to make, which devices you're targeting, and how you've been invoking the compiler. You might think of there being four existing versions of MSP430 support for gcc:

Re: [Mspgcc-users] Combining multiple object files into a relocatable file and error in relocation entry.

2010-12-23 Thread Peter Bigot
I had played with this a little, and discovered (as you did) the necessity of including the -mmcu option for the linker (without it, certain constants such as the stack address get a default value that's wrong unless you're targeting an MSP430F110 or something similar). I got to the point where I

Re: [Mspgcc-users] Notice of elimination of genericized mcu names in uniarch

2010-12-23 Thread Jesse Frey
I have been using -mmcu=msp430x2618 if I understand correctly this will not be supported in the future and I will have to use -mmcu=msp430f2618 which does not work with the version that I have. what I would like to be able to do is to write code and makefiles that will work for all compilers