This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi, I have tried the following an has worked. First, configured and built the bootstrap compiler using: ../gcc-3.3.2/configure --target=arm-elf --prefix=/usr/local/arm --host=i686-pc-linux-gnu --with-newlib --without-headers --enable-languages=c make make install then compiled the newlib with the bootstrap compiler. with ../newlib-1.11.0/configure --target=arm-elf --prefix=/usr/local/arm --host=i686-pc-linux-gnu make make install and then built the complete cross gcc including the newlib libraries. ../gcc-3.3.2/configure --target=arm-elf --prefix=/usr/local/arm --host=i686-pc-linux-gnu make make install Everything has worked OK. What's the difference between arm-linux and arm-elf targets ?. I think that arm-linux is to be used with glibc libraries and arm-elf is to be used with newlib. Is this correct ?. I am new in this and have read that for embedded applications is better to use newlib rather than glibc. The target environment I pretend to run the application is a at91rm9200dk board or something similar but based it arm920t architecture. Thanks for helping me with this. Best Regards, Aitor __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |