Jack Howarth wrote:
Do we have any other targets that link gcc (and xgcc) with the shared libgcc? I see that i386 and x86_64 linux creates a gcc (and xgcc) linked to the static libgcc. If any other targets use a shared libgcc for gcc (and xgcc) they may be broken as well.
That's a good hint; it certainly seems possible that this is indeed somehow related to the problem. However, I don't know the answer to your question. Because of the convoluted way in which the GCC build process works (in particular, that binaries are run out of the $objdir, which has a different layout than the eventual installation), making the driver depend on shared libraries created during the build is certainly going to be tricky. In particular, on most platforms LD_LIBRARY_PATH (or equivalent) will have to be set just so whenever xgcc is run.
-- Mark Mitchell CodeSourcery [EMAIL PROTECTED] (650) 331-3385 x713
