Build problem(libgcj on linuxppc(R5))

[Will Sloan]

Should it appear in libgcc or libgcc2?  It would appear that libgcc2.a
never got built.  Any ideas??

Will
Tom Tromey wrote:

> >>>>> "Will" == Will Sloan <wsloan@occamnetworks.com> writes:
>
> Will> I'm trying to build libgcj in a cross enviorment.  In the native
> Will> (Redhat 6.0 system), libgcj compiled fine, so I went looking
> Will> through /lib and /usr/lib to see what library had __throw.
> Will> Thats when I found libstdc++.  Then I went to my linuxppc
> Will> machine (R5) and looked at libstdc++ and sure enough __throw was
> Will> there.  Therefore I concluded that my libstdc++ build must be
> Will> bad.  My question now is how to fix this??
>
> __throw should appear in libgcc, not libstdc++.
> libgcc isn't in /lib or /usr/lib.  On my machine it is below
> /usr/lib/gcc-lib.
>
> First we should check to make sure your link is linking in this
> library.  You can do this by running the link by hand and adding the
> "-v" argument to the command-line.  Then examine the actual linker
> command to see what is really linked in (gcj links in special
> libraries behind your back).
>
> Tom