This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/21277] Runtime error with C++ shared library and --disable-shared


------- Additional Comments From info at yourkit dot com  2005-05-02 08:15 -------
> OK, the fundamental problem is that you're trying to build shared libraries with
a compiler configured with --disable-shared.  That's not really intended (and
might cause problems for exception propagation in C++).

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.

Without --disable-shared we had other problems linking 64 bit code statically.

Anyway, option --disable-shared exists, and is documented. So it should either
properly work (for platforms it is supported for), or be dropped (for platforms
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? :)

> The fix is indeed to recompile every GCC library with -fPIC.  Try to configure
at toplevel --with-pic, but I'm not sure the option is valid there.  Otherwise
you'll need to specifically configure libstdc++-v3 --with-pic.

Thank you for the suggestion. I'll try it now, and will let you know whether it
helps.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21277


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]