> And now, look at official ARM arm-gcc building script: it builds > gcc twice, it copy first copy of gcc somewhere, to remove later, it > wants to find some linux-specific headers in process, etc, etc, > etc. Also, it uses
There are two parts to gcc: the compiler binaries, and the support runtime. The support runtime needs to know what libraries you're using. Linux-based targets are tricky because you need a working gcc to build glibc, and you need a working glibc to build gcc. For non-linux embedded, it's easier - you do "make all-host" in gcc, and it only builds the compiler. So you can do the simple binutils/gcc configure/make/install and it works, with an extra step (make all-target) or two to build the runtime libraries of choice. ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
