This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Testing ARM-Linux toolchain
- From: "Stevens, Peter" <StevensP at spielo dot com>
- To: <gcc-help at gcc dot gnu dot org>
- Date: Tue, 18 May 2004 10:57:00 -0300
- Subject: Testing ARM-Linux toolchain
All,
I have successfully built a cross compiler tool chain for ARM-Linux. But, I have a few questions about how to "properly" test it. Given the fact that GCC and it's related tools include testsuites, I would like to use them. Thing is, my target hardware platform wont arrive for awhile and I would like to begin testing the tool chain before it does. I have seen/read documents describing the use of GDBs simulator to test the toolchain, but I am still abit confused as to how/ or if this is even possible given my current setup.
Host Platform: x86 running RedHat
Target Platform: Intel Development Board with PXA27X processor
Toolchain Versions: GCC 3.3.2
GLibC 2.3.2
Bin Utilities 2.14
>From what understand, I would have to switch to newlib inorder to make things work ?? Why might this be true ... some explantions suggest glibc needs to make system calls ... does this imply that newlib does not ??
As mentioned I am abit confused with this whole cpu simulator thing .. Is this the only way I can reliably test my toolchain ? If anybody can body speak from experience as to the best way to test a toolchain, maybe some other methods ... it would be highly appreciated.
Thanks,
Peter