http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56750
--- Comment #5 from Mike Frysinger ---
(In reply to Eric Botcazou from comment #4)
that is an end user's decision. the build scripts really have no business
forcing this on all random tools including gdb. the bootstrap logic makes
sense for boo
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56750
--- Comment #4 from Eric Botcazou ---
> 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.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56750
Jakub Jelinek changed:
What|Removed |Added
CC||aoliva at gcc dot gnu.org,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56750
--- Comment #2 from Eric Botcazou ---
IMO forcing -static-libstdc++ is a progress, especially on non-Linux platforms,
so I don't really see what needs fixing here. Of course people might disagree
and tailor this to their needs (and write a patch)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56750
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1 f
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56750
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
Version|unknown
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56750
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |4.9.0
Summary|static -lstdc++
