Electronics & Programming

develissimo

Open Source electronics development and programming

  • You are not logged in.
  • Root
  • » MSPGCC
  • » [Mspgcc-users] Cygwin woes, linker tricks. Re: Both COMPLING and LINKING for msp430x2131 fails with latest windows binary installer [RSS Feed]

#1 Nov. 12, 2005 20:44:17

John H.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[Mspgcc-users] Cygwin woes, linker tricks. Re: Both COMPLING and LINKING for msp430x2131 fails with latest windows binary installer


First, by compiling binutils from its daily snapshot, I got a new
msp430-ld and a new set of automatically generated linker scripts that
works.

msp430-ld from binutils was compiled under cygwin and there is an
ugly, though harmeless, cygwin dll mismatch message. Hence I am not
offering it for download: it should be compiled to match the cygwin
dlls used by the rest of the mspgcc distribution.

It would be nice if we could get rid of cygwin altogether, however
there are known issues using the cygwin free MinGW/MSYS tools with
regard to cross compilers, such as collect2 for the compiler and
readline for gdb. However codesourcery.com have overcome these
problems for its GNU ARM distribution. Apparently they get paid by ARM
to maintain and update the distribution. There is a good chance their
gdb for ARM will work in Dev-C++ and possibly Eclipse.

With regard to Nico's comments below verbose linker message can be
observed by adding -Wl,--verbose in the makefile

${NAME}.elf: ${OBJECTS}
${CC} -mmcu=${CPU} -o $@ ${OBJECTS} -Wl,--verbose

Default startup files can be bypassed with -Wl,-nostartfiles

There is an option to avoid using standard libraries.

A linker script can be specified with -T(script)

This type of flexibilty is very attractive when you want to use you
own startup files, standard library replacements and linker scripts.

John Heenan


From: N. Coesel <n...@nc...>

>The linker vlag only tells the linker which scripts and libraries to
use.
>There is no black magic involved. You can specify all these on the
command
>line of ld. If you run ld in a verbose mode with a known emulation,
you'll
>see which files are used. Copies references to these files into the
>makefile and you're well on your way.

>Nico Coesel

Offline

#2 Nov. 13, 2005 02:28:09

Steve U.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

[Mspgcc-users] Cygwin woes, linker tricks. Re: Both COMPLING and LINKING for msp430x2131 fails with latest windows binary installer


John Heenan wrote:It would be nice if we could get rid of cygwin altogether, however
there are known issues using the cygwin free MinGW/MSYS tools with
regard to cross compilers, such as collect2 for the compiler and
readline for gdb. However codesourcery.com have overcome these
problems for its GNU ARM distribution. Apparently they get paid by ARM
to maintain and update the distribution. There is a good chance their
gdb for ARM will work in Dev-C++ and possibly Eclipse.You can't get rid of Cygwin, so forget it. We used to build with Cygwinand MinGW. The MinGW versions ran faster, but had many many problems.Curing those is a *major* project, as the MinGW folk have found. The CCEfolk also seem to have figured this out, as CCE using Cygwin too.Just live with Cygwin. It works well.

Regards,
Steve

Offline

  • Root
  • » MSPGCC
  • » [Mspgcc-users] Cygwin woes, linker tricks. Re: Both COMPLING and LINKING for msp430x2131 fails with latest windows binary installer [RSS Feed]

Board footer

Moderator control

Enjoy the 18th of November
PoweredBy

The Forums are managed by develissimo stuff members, if you find any issues or misplaced content please help us to fix it. Thank you! Tell us via Contact Options
Leave a Message
Welcome to Develissimo Live Support