Mike Hearn wrote:
On Mon, 12 Dec 2005 13:20:29 -0600, Bob Jamison wrote:
Now inkscape will link against the static version of libstdc++, and 'ldd' will no longer list it as a dep.
The risk is that this interferes with the system libstdc++.
Hi, Mike!
I'm not sure what you mean. Do you mean (pick one):
a) Installing Inkscape on someone's box might interfere with their normal use of libstdc++.so? I don't see how this is a problem. Only a statically-bound Inkscape would be bound permanently to static stdc++ objects. Other system objects that look for the .so's would continue to do so. The only confusion that I could see would be if we make a libinkscape.so with a statically-bound stdc++.... other clients that use the shared object might load the wrong symbols, but only if we screw it up. This is moot, however, since exposing Inkscape c++ objects would negate the value of statically linking the whole blob anyway.
b) Or do you mean the gcc "make install" itself damaging the development box? If so, just let it go to /usr/local like it wants, or use --prefix=something to put it in a safe place, then only set PATH and LD_LIBRARY_PATH for that build. ../configure --enable-languages=c,c++ --disable-shared --prefix=/usr/local/gcc402 would work nicely.
Earlier I made a practice of periodically uploading Linux builds with everything C++ statically linked, including stdc++, and also Boehm. I built them on FC3 and FC4 with various versions of g++, and never had a problem with running them on other gcc versions or distros.
Hopefully the c++ ABI might actually freeze soon. It's been gelling for a long time now. ;-)
bob