public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/56750] [4.8/4.9 Regression] static -lstdc++ logic bleeds into all subdirs
Date: Tue, 18 Feb 2014 16:41:00 -0000 [thread overview]
Message-ID: <bug-56750-4-zKDl7m509l@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56750-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56750
--- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Well, if you can link dynamically, you should, if say libstdc++ contains
> some security bug and gdb isn't built in the combined tree with gcc, then
> I'd say it is highly undesirable to link it statically.
Your point of view is clearly too Linux-centric here. :-) I can assure you
that the last thing people want on Solaris on HP-UX is to have to install
shared libraries to run GDB.
next prev parent reply other threads:[~2014-02-18 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 5:33 [Bug bootstrap/56750] New: " vapier at gentoo dot org
2013-09-04 8:27 ` [Bug bootstrap/56750] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org
2013-11-22 10:42 ` rguenth at gcc dot gnu.org
2014-02-18 15:17 ` jakub at gcc dot gnu.org
2014-02-18 15:53 ` ebotcazou at gcc dot gnu.org
2014-02-18 16:01 ` jakub at gcc dot gnu.org
2014-02-18 16:41 ` ebotcazou at gcc dot gnu.org [this message]
2014-02-18 17:25 ` vapier at gentoo dot org
2014-05-22 9:03 ` [Bug bootstrap/56750] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-09-09 22:23 ` [Bug bootstrap/56750] [4.8/4.9/5 " vapier at gentoo dot org
2014-12-19 13:29 ` jakub at gcc dot gnu.org
2015-03-24 18:40 ` steven at gcc dot gnu.org
2015-06-23 8:23 ` [Bug bootstrap/56750] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 20:01 ` [Bug bootstrap/56750] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:30 ` jakub at gcc dot gnu.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=bug-56750-4-zKDl7m509l@http.gcc.gnu.org/bugzilla/ \
--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: link
Be 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).