re PR libstdc++/47058 ("--enable-maintainer-mode --disable-werror" wrongly...
re PR libstdc++/47058 ("--enable-maintainer-mode --disable-werror" wrongly upgrades warnings to errors in libstdc++) 2012-02-17 Benjamin Kosnik <bkoz@redhat.com> PR libstdc++/47058 * acinclude.m4 (GLIBCXX_ENABLE_WERROR): New. (GLIBCXX_EXPORT_FLAGS): Add -Wabi to WARN_FLAGS * configure.ac: Use it. * fragment.am: Set WERROR_FLAG conditionally on --disable-werror. * configure: Regenerate. * python/Makefile.in: Same. * Makefile.in: Same. * doc/Makefile.in: Same. * include/Makefile.in: Same. * po/Makefile.in: Same. * python/Makefile.in: Same. * src/Makefile.in: Same. * src/c++11/Makefile.in: Same. * src/c++98/Makefile.in: Same. * testsuite/Makefile.in: Same. From-SVN: r184349
Showing
- libstdc++-v3/ChangeLog 19 additions, 0 deletionslibstdc++-v3/ChangeLog
- libstdc++-v3/Makefile.in 3 additions, 1 deletionlibstdc++-v3/Makefile.in
- libstdc++-v3/acinclude.m4 12 additions, 1 deletionlibstdc++-v3/acinclude.m4
- libstdc++-v3/configure 48 additions, 11 deletionslibstdc++-v3/configure
- libstdc++-v3/configure.ac 1 addition, 0 deletionslibstdc++-v3/configure.ac
- libstdc++-v3/doc/Makefile.in 3 additions, 1 deletionlibstdc++-v3/doc/Makefile.in
- libstdc++-v3/fragment.am 7 additions, 1 deletionlibstdc++-v3/fragment.am
- libstdc++-v3/include/Makefile.in 3 additions, 1 deletionlibstdc++-v3/include/Makefile.in
- libstdc++-v3/libsupc++/Makefile.in 3 additions, 1 deletionlibstdc++-v3/libsupc++/Makefile.in
- libstdc++-v3/po/Makefile.in 3 additions, 1 deletionlibstdc++-v3/po/Makefile.in
- libstdc++-v3/python/Makefile.in 3 additions, 1 deletionlibstdc++-v3/python/Makefile.in
- libstdc++-v3/src/Makefile.in 3 additions, 1 deletionlibstdc++-v3/src/Makefile.in
- libstdc++-v3/src/c++11/Makefile.in 3 additions, 1 deletionlibstdc++-v3/src/c++11/Makefile.in
- libstdc++-v3/src/c++98/Makefile.in 3 additions, 1 deletionlibstdc++-v3/src/c++98/Makefile.in
- libstdc++-v3/testsuite/Makefile.in 3 additions, 1 deletionlibstdc++-v3/testsuite/Makefile.in
Loading
Please register or sign in to comment