Originally Posted by knc1
I assume from the filename this is a C not a C++ source, so ...
That will take care of the warning messages about the runtime (if CS built a static libgcc - I haven't checked for that).
GM's choice of 2010q1-202 (a CS product, prior to purchase by MG) is one very close to what lab126 was using on the K5. "We stock" the 2010-09 for that purpose, one (six months later) release. Shouldn't be much difference between the two.
For "new work" such as this, using the most recent release (2012.03-57) is the way to go. You shouldn't run into the corner cases where you need to match the original compiler version.
Some of the work GM does, does run into them and does require a "best match" of the tool chain.
While cross compiling, try setting your PATH to:
Then: gcc --version
should report the arm gcc (and also make all references to the tool chain components grab the arm components).
I can't see how, when you enter:
that you are picking up the compiler that is being reported in the messages.
There must be some other local settings that you have that make it do that.
Check those, or post them for review here.
Well I can answer that. I was tired of typing the long version so I just ln -s
'd the shorter triplet to the long ghueabi version. Should have said, my bad.
The error only exhibits when sing the alsalib and only when used static.
Since I am happy with shared I will file this under - weird
- and move on.
Thanks v much!