------- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-05-02 09:05 ------- > We must link our .so statically with all the gcc stuff to make sure it runs on > every Solaris. Shipping libstd++.so with our shared library is not very > suitable for us, because it makes product download size bigger.
5 MB uncompressed for 32-bit, 6 MB uncompressed for 64-bit! > Anyway, option --disable-shared exists, and is documented. So it should either > properly work (for platforms it is supported for), or be dropped (forplatforms > where it is not supported). While there's nothing said it is not supported for > Solaris, all its improper work is a bug, and nothing but a bug. Isn't it? :) There is nothing wrong in the current behavior of --disable-shared: it builds static libraries the way static libraries should be built. Your practice of building shared libraries with a compiler configured with --disable-shared looks far more questionable to me; if I were to change something, I'd simply reject -shared in that case. Note for example that a shared libgcc is required on Solaris for exception propagation accross shared libraries. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21277
