Can the script be used to build support for MSP430X? Following Sergey's instructions I have built binutils and the binaries for mspgcc, but I am still having trouble with the c library (I can almost build a test program but ld says it cannot find "-lc" - I don't link this explicitly, so I don't know what is going on). When building from the makefile in packaging, some things were built to "/build/installed" while others were built to "~/packaging/build/installed" (the intended destination). I am trying to build it all in cygwin, perhaps why I am having so much trouble? As sad as it makes me I am about to stop trying and move to Code Composer Essentials. It is poor compared to working with mspgcc but I can't waste any more time trying to build this. I may look at converting back when there is a binary/windows install available.
Thanks for the help though guys. I hope mspgcc gets on its feet again and we see support for MSP430X for everyone. - Wayne Sent via BlackBerry® from Vodafone -----Original Message----- From: Simsys Miller <[email protected]> Date: Mon, 9 Feb 2009 19:12:56 To: GCC for MSP430 - http://mspgcc.sf.net<[email protected]> Subject: Re: [Mspgcc-users] Building the toolchain Hi, that's right. If You are honest, you need some things around, also documented on the wiki: http://apps.sourceforge.net/mediawiki/mspgcc/index.php?title=Linux_installation cheers simsys 2009/2/9 Rick Jenkins <[email protected]>: > A lot of people seem to have difficulty with building the toolset. The > developers maintain a script to do the whole thing, and it has always worked > well for me. I use the following crude stub script to activate it: > > #!/bin/bash > # > # This is the "official" build, using the latest script > # from CVS, which is maintained by the developers. > # > # Before running this for the first time as an ordinary user, > # as root: > # > # mkdir -p /opt/mspgcc > # chown $USER.$USER /opt/mspgcc > # > #``$USER`` should be replaced with the login name of the user that > # will build the toolchain > # > # To use the resulting toolchain, put the path in your .bashrc > # > # PATH=$PATH:/opt/mspgcc/bin > > mkdir -p mspgcc/sf > cd mspgcc/sf > cvs -d:pserver:[email protected]:/cvsroot/mspgcc login > cvs -z3 -d:pserver:[email protected]:/cvsroot/mspgcc > co -P . > cd packaging > make folders > # Replace "3.3.6" with the version number of the gcc you use to compile. > # It should not be a gcc4 version. the command > # gcc-config -l > # will list available compilers on your system > CC=gcc-3.3.6 make build > > This rebuilds the entire toolchain, so that you know you are up-to-date, > cumbersome but secure. > > > > > -- > Rick Jenkins <[email protected]> > Hartman Technica http://www.hartmantech.com > Phone +1 (403) 230-1987 > 221 35 Avenue. N.E., Calgary, Alberta, Canada T2E 2K5 > > ------------------------------------------------------------------------------ > Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) > software. With Adobe AIR, Ajax developers can use existing skills and code to > build responsive, highly engaging applications that combine the power of local > resources and data with the reach of the web. Download the Adobe AIR SDK and > Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
