From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@ericsson.com>
Subject: [PATCH 5/6] [C++] Drop -fpermissive hack
Date: Wed, 18 Nov 2015 16:40:00 -0000 [thread overview]
Message-ID: <1447864802-24016-6-git-send-email-palves@redhat.com> (raw)
In-Reply-To: <1447864802-24016-1-git-send-email-palves@redhat.com>
Both x86_64 GNU/Linux and x86_64 mingw-w64 build cleanly with
--enable-targets=all. Let's drop the -fpermissive hack, in order to
let the buildbot catch C++ build regressions for us.
gdb/ChangeLog:
2015-11-18 Pedro Alves <palves@redhat.com>
* build-with-cxx.m4 (GDB_AC_BUILD_WITH_CXX): Remove -fpermissive.
* configure: Regenerate.
gdb/gdbserver/ChangeLog:
2015-11-18 Pedro Alves <palves@redhat.com>
* configure: Regenerate.
---
gdb/build-with-cxx.m4 | 3 +--
gdb/configure | 3 +--
gdb/gdbserver/configure | 3 +--
3 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/gdb/build-with-cxx.m4 b/gdb/build-with-cxx.m4
index 8802f4d..b6284fd 100644
--- a/gdb/build-with-cxx.m4
+++ b/gdb/build-with-cxx.m4
@@ -32,8 +32,7 @@ AC_DEFUN([GDB_AC_BUILD_WITH_CXX],
[enable_build_with_cxx=no])
if test "$enable_build_with_cxx" = "yes"; then
- # We're using -fpermissive as shortcut for now.
- COMPILER='$(CXX) -fpermissive'
+ COMPILER='$(CXX)'
else
COMPILER='$(CC)'
fi
diff --git a/gdb/configure b/gdb/configure
index fd7ea1c..8ef3cf2 100755
--- a/gdb/configure
+++ b/gdb/configure
@@ -5015,8 +5015,7 @@ fi
if test "$enable_build_with_cxx" = "yes"; then
- # We're using -fpermissive as shortcut for now.
- COMPILER='$(CXX) -fpermissive'
+ COMPILER='$(CXX)'
else
COMPILER='$(CC)'
fi
diff --git a/gdb/gdbserver/configure b/gdb/gdbserver/configure
index 409f42b..4b9aa95 100755
--- a/gdb/gdbserver/configure
+++ b/gdb/gdbserver/configure
@@ -4827,8 +4827,7 @@ fi
if test "$enable_build_with_cxx" = "yes"; then
- # We're using -fpermissive as shortcut for now.
- COMPILER='$(CXX) -fpermissive'
+ COMPILER='$(CXX)'
else
COMPILER='$(CC)'
fi
--
1.9.3
next prev parent reply other threads:[~2015-11-18 16:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 16:40 [PATCH 0/6] [C++] Drop -fpermissive hack, enable -Werror Pedro Alves
2015-11-18 16:40 ` [PATCH 4/6] [C++] breakpoint.c: "no memory" software watchpoints and enum casts Pedro Alves
2015-11-18 16:40 ` [PATCH 1/6] [C++] remote.c: Avoid enum arithmetic Pedro Alves
2015-11-18 16:40 ` [PATCH 3/6] [C++] s390: Fix enum gdb_syscall conversion Pedro Alves
2015-11-18 16:40 ` Pedro Alves [this message]
2015-11-18 16:40 ` [PATCH 2/6] [C++] linux-thread-db.c: dladdr cast Pedro Alves
2015-11-18 16:48 ` [PATCH 0/6] [C++] Drop -fpermissive hack, enable -Werror Simon Marchi
2015-11-18 16:49 ` [PATCH 6/6] [C++] Default to -Werror in C++ mode too Pedro Alves
2015-11-18 17:44 ` [PATCH 0/6] [C++] Drop -fpermissive hack, enable -Werror Yao Qi
2015-11-18 17:53 ` Pedro Alves
2015-11-19 11:28 ` Yao Qi
2015-11-19 15:14 ` Pedro Alves
2015-11-20 9:46 ` Yao Qi
2015-11-20 11:21 ` Pedro Alves
2015-11-24 11:01 ` Yao Qi
2015-11-24 13:17 ` Pedro Alves
2015-11-24 14:37 ` Joel Brobecker
2015-11-24 13:19 ` Pedro Alves
2015-11-19 15:17 ` Pedro Alves
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=1447864802-24016-6-git-send-email-palves@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
/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).