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
