arm/iwmmxt VFP errors during linking

[Dimitry Andric]

On 2005-04-11 at 17:31:49 Daniel Kegel wrote:

> No.  It's a matter of using the right version of gcc.
> libstdc++.so.5 is used with gcc-2.95.x, and
> libstdc++.so.6 is used with gcc-3.x.

This isn't true, here's the official list:

    * gcc-3.0.0: libstdc++.so.3.0.0
    * gcc-3.0.1: libstdc++.so.3.0.1
    * gcc-3.0.2: libstdc++.so.3.0.2
    * gcc-3.0.3: libstdc++.so.3.0.2 (Error should be libstdc++.so.3.0.3)
    * gcc-3.0.4: libstdc++.so.3.0.4
    * gcc-3.1.0: libstdc++.so.4.0.0
    * gcc-3.1.1: libstdc++.so.4.0.1
    * gcc-3.2.0: libstdc++.so.5.0.0
    * gcc-3.2.1: libstdc++.so.5.0.1
    * gcc-3.2.2: libstdc++.so.5.0.2
    * gcc-3.2.3: libstdc++.so.5.0.3 (Not strictly required)
    * gcc-3.3.0: libstdc++.so.5.0.4
    * gcc-3.3.1: libstdc++.so.5.0.5
    * gcc-3.3.2: libstdc++.so.5.0.5
    * gcc-3.3.3: libstdc++.so.5.0.5
    * gcc-3.4.0: libstdc++.so.6.0.0
    * gcc-3.4.1: libstdc++.so.6.0.1


> You have to go find a gcc-2.9x toolchain if you really need to
> interoperate with libappbase-xscale-r.so.

Instead, he'll need gcc 3.3.x.  In general, it's of course wisest to
compile everything with the same toolchain.  At least approximately
the same version...

Nick, can you ask your library supplier to give you some version
numbers of the components of their toolchain?


> Alternately, you could convince whoever gave you that shared library
> to recompile with your toolchain.

I know how hard this can be, with proprietary software vendors...  And
sometimes you need to spend so much time helping them getting another
toolchain working for their build process, that you almost could have
rewritten their library yourself. ;)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 183 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/crossgcc/attachments/20050411/de79ae6c/attachment.sig>