![](https://secure.gravatar.com/avatar/58a5209b61cc09379468fe48275f2ddf.jpg?s=120&d=mm&r=g)
On Sat, 28 Aug 2004 14:30:17 -0700, Bryce Harrington wrote:
I think this would be a good solution especially due to the fact that gc must be compiled with the --enable-cplusplus option, which it appears few if any pre-packaged versions of gc have, anyway.
If the gc package were smaller, I'd even be tempted to suggest incorporating it into the inkscape codebase, but at over 200 files I think that would be way too much bloat.
The autopackages of 0.40 already statically link libgc for exactly this reason: on the few systems that already have it installed, it usually lacks C++ support. On the tiny number of systems that have it with C++ support, the recent C++ ABI breakage would stop it from being usable anyway.
I'm pondering static linking GTKmm as well, again because there's no stable C++ ABI on Linux yet. The DSO is only about 700k, and in this case I'm not sure the effort of having separate packages, C++ ABI detection, rpath mangling and so on is really worth it.
thanks -mike