public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/21277] Runtime error with C++ shared library and --disable-shared Date: Mon, 02 May 2005 09:05:00 -0000 [thread overview] Message-ID: <20050502090531.2954.qmail@sourceware.org> (raw) In-Reply-To: <20050429073316.21277.info@yourkit.com> ------- 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
next prev parent reply other threads:[~2005-05-02 9:05 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-29 7:33 [Bug c++/21277] New: gcc 4.0 fails to statically link on Solaris SPARC 64 bit info at yourkit dot com 2005-04-29 7:39 ` [Bug c++/21277] " info at yourkit dot com 2005-04-29 7:39 ` pinskia at gcc dot gnu dot org 2005-04-29 7:39 ` [Bug libstdc++/21277] " pinskia at gcc dot gnu dot org 2005-04-29 7:55 ` pcarlini at suse dot de 2005-04-29 8:27 ` [Bug c++/21277] " info at yourkit dot com 2005-04-29 12:40 ` [Bug target/21277] " pinskia at gcc dot gnu dot org 2005-04-29 15:25 ` [Bug c++/21277] " info at yourkit dot com 2005-04-29 19:19 ` pinskia at gcc dot gnu dot org 2005-04-29 19:20 ` pinskia at gcc dot gnu dot org 2005-04-30 20:46 ` [Bug target/21277] Runtime error with C++ shared library and --disable-shared ebotcazou at gcc dot gnu dot org 2005-05-02 6:59 ` info at yourkit dot com 2005-05-02 7:16 ` ebotcazou at gcc dot gnu dot org 2005-05-02 7:19 ` info at yourkit dot com 2005-05-02 7:23 ` info at yourkit dot com 2005-05-02 7:27 ` ebotcazou at gcc dot gnu dot org 2005-05-02 7:33 ` info at yourkit dot com 2005-05-02 7:57 ` ebotcazou at gcc dot gnu dot org 2005-05-02 8:15 ` info at yourkit dot com 2005-05-02 9:05 ` ebotcazou at gcc dot gnu dot org [this message] 2005-05-02 9:25 ` info at yourkit dot com 2005-05-02 9:47 ` info at yourkit dot com 2005-05-02 9:54 ` ebotcazou at gcc dot gnu dot org 2005-05-02 9:58 ` ebotcazou at gcc dot gnu dot org 2005-05-02 11:10 ` info at yourkit dot com 2005-05-02 15:54 ` ebotcazou at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20050502090531.2954.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).