[Bug bootstrap/60634] [4.9] Build x86_64-unknown-linux-gnu with --disable-libstdc__-v3 is broken

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60634

Andrew Pinski pinskia at gcc dot gnu.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Andrew Pinski pinskia at gcc dot gnu.org ---
If you don't want libstdc++, then you should disable C++ instead of disabling
libstdc++.  Anyways won't fix.

[Bug bootstrap/60634] [4.9] Build x86_64-unknown-linux-gnu with --disable-libstdc__-v3 is broken

[jakub at gcc dot gnu.org]

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

Jakub Jelinek jakub at gcc dot gnu.org changed:

   What|Removed |Added

 CC||jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek jakub at gcc dot gnu.org ---
What is it useful for to configure gcc that way?  And, both libsanitizer and
libcilkrts really require libstdc++, so IMNSHO if you disable that, you should
disable those too.

[Bug bootstrap/60634] [4.9] Build x86_64-unknown-linux-gnu with --disable-libstdc__-v3 is broken

[aivchenk at gmail dot com]

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

--- Comment #2 from Alexander Ivchenko aivchenk at gmail dot com ---
(In reply to Jakub Jelinek from comment #1)
 What is it useful for to configure gcc that way?  
The stdc++ library is built and shipped separately from the compiler.
 And, both libsanitizer and libcilkrts really require libstdc++, so IMNSHO if
 you disable that, you should disable those too.
Do we have any mechanism to check that on configure time?