"Gary Funck" <[EMAIL PROTECTED]> writes: > Ian Lance Taylor wrote (in part): > > Telling the dynamic linker about a dynamic libgcc is still a problem, > > but that is a problem whereever you put the compiler. > > If I'm not interested in build a dynamically linked gcc, or building > libgcc and related libraries as dynamic libraries, can I simply assert > --disable-shared when configuring gcc, and thus ensure that the resulting > compiler binaries can be easily moved around?
Pedantically, the compiler binaries can be moved around in any case. The only issue with a shared libgcc is whether the dynamic linker can find it when you run a program linked against it. It is of course possible to fix this, whereever the library winds, up by using /etc/ld.so.conf (if available) or LD_LIBRARY_PATH (or equivalent). If you use --disable-shared when configuring gcc, then it won't build a shared libgcc. But my understanding is that then you won't be able to throw and catch exceptions between shared libraries. See the discussion of the -shared-libgcc option. Ian
