[Mspgcc-users] [not quite SOLVED] Re: cannot open linker script file memory.x: No such file or directory

[Yama P. <yam...@gm...>]

1)
do use the -mmcu flag
for the -mmcu flag, use the scripts in /usr/msp430/lib/ldscripts (like 
msp430g2210)
and not those in /etc/msp430/include (like msp430x16x)

example (that works):
msp430-gcc -mmcu=msp430g2210 myfile.c -o output.elf

2) other thoughts:
I am not too happy about using -mmcu flags, as it adds one more step.
I prefer in-code include. Maybe a Path addition would solve this. Being 
a noob, that will be another hour exploration

All in all, this whole process to install the toolchain by retrieving 
files and install from them is too laborious, and definitely does not 
compare well with the one liner:
  sudo yum install msp430-libc mspdebug
as taught in http://processors.wiki.ti.com/index.php/OLPC_XO-1

The goal being to make the ramp-up very easy, this is not quite it yet. 
Maybe redirecting yum install to Robert's repository would fix that? No 
idea how to do that either :-p

3) Now, if it lets me do UART, then maybe I'll be ahead of where I wuz :-)


On 11/28/2012 01:57 PM, Yama Ploskonka wrote:
> please help!
>
> when trying to compile, I get
>
> /usr/lib/gcc/msp430/4.6.3/../../../../msp430/bin/ld: cannot open 
> linker script file memory.x: No such file or directory
> collect2: ld returned 1 exit status
>
> - This says to re-emerge msp430mcu....
> https://github.com/radhermit/msp430-overlay
> no idea how to do that :-(
>
> - There was some advice in 2011 by Peter to the effect of "passing the 
> -mmcu flag"
> http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10095
> I tried msp430.gcc -mmcu=msp430x16x myfile.c
> no luck.
> msp430x16x exists indeed in /etc/msp430/include - I even tried full 
> path in the code
> #include </etc/msp430/include/msp430x16x.h>
>
> I'm stuck...
> might be something obviously simple, I hope...
>
> Fedora 17, OLPC OS.
> I reinstalled the OS, ran all the install process again (this time 
> with /yum --nogpgcheck install /in hopes that would "connect" things 
> better), and by now have (apparently) all up to date gcc, binutils, 
> libc and mcu.
>