[Bug other/14704] -static-libgcc option appears non-functional under Solaris

[stefan dot jankowski at informatik dot uni-freiburg dot de]

------- Additional Comments From stefan dot jankowski at informatik dot uni-freiburg dot de  2004-04-20 15:10 -------
The manual only mentions (as far as I can tell from searching it for the string
"shared-libgcc") that the G++ and GCJ drivers activate -shared-libgcc because it
is needed for exception handling (OpenSSL's Makefile however does not contain
the string "++"). The manual also says that one needs to link plain C stuff that
is supposed to handle exceptions with the G++ or the GCJ driver or with an
explicit -shared-libgcc but does not say anything about adding it automagically.
(And I don't find the string "shared-libgcc" in the transcript of a build run
with CFLAGS containing --verbose). It is true however, that the inclusion of
libgcc_s.so.1 does not happen for every C source file.

Meanwhile I have implemented the solution proposed in

  http://www.mail-archive.com/openssl-dev@openssl.org/msg16142.html

and with that GCC 3.3.2 will build .so's without dependencies to libgcc_s. So
GCC /can/ build OpenSSL (and probably others) that way, although I am not sure
that this measure will not break things at runtime later. Is this risky, and if
so, to what degree?


-- 


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