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, Kai > > So your best bet is to use glibc as the C library... You can 'bootstrap' > your 'xscale-linux-gnu' target toolchain using a prebuilt glibc for some > 'arm-linux-gnu' toolchain available on the net just as you can use a > 'i386-linux-gnu' target glibc to bootstrap a 'i686-linux-gnu' target > toolchain. Or try those scripts from Dan & Co. > Thank you so much for the great explanation! I will study your letter carefully. I know the problem will be solved using glibc. However, I am using a simulator in my research. The simulator assumes newlib, maybe because newlib is much easier. So if I change to glibc, I have to modify the simulator too. I don't think the current idea I am working on deserves the effort. So I will simply use the benchmarks that can be compiled I guess. > Ok, one can build a complete toolchain for 'xscale-linux-gnu' for free, and one > can build the kernel etc. for Linux/XScale also for free, but getting the XScale > HW for free is not that easy... So where you are going to try the SPEC2000 tests > if not having the HW itself? With the '-elf' and '-coff' one has the ARM-simulator > in GDB, but with Linux this way doesn't work... > I am doing research in a university so getting the HW is not a big problem. But lots of research is done in simulator since it can be easily modified... Best Regards Tao ------ 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] |