https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51450
--- Comment #7 from Sam James ---
Possibly fixed by:
commit 11869b9c9eb8bcc8cb6a615141f522a447377324
Author: Gary V. Vaughan
Date: Sat Nov 26 11:06:35 2011 +0700
m4: fix logic error leading to -fno-rtti being added wrongly.
* m4/lib
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51450
--- Comment #6 from Andrew Pinski ---
configure:18495: checking if gcc supports -fno-rtti -fno-exceptions
configure:18513: gcc -c -g -fno-rtti -fno-exceptions conftest.c >&5
cc1: warning: command-line option '-fno-rtti' is valid for C++/D/ObjC+
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51450
--- Comment #5 from Eric Gallager ---
Is this an issue with upstream libtool, too, or just GCC's patched version of
it?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51450
Eric Gallager changed:
What|Removed |Added
CC||jay.krell at cornell dot edu
--- Comment
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51450
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |NEW
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51450
--- Comment #3 from Andrew Pinski 2012-01-30
20:18:31 UTC ---
Looks like there are two different places in configure which test -fno-rtti and
-fno-exceptions:
One around line 28658 (which does not use lt_simple_compile_test_code
And one around li
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51450
--- Comment #2 from christophe.lyon at st dot com 2012-01-30 09:23:27 UTC ---
I noticed this about an official release; I am not sure which one it was when I
entered this report, but it is at least true for GCC-4.6.2.
I have just checked
http://gc
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51450
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
