And also error when I add "-g"
Excellent, thanks for the feedback. I believe that the modified
configure test will solve this issue, and will be monitoring
gcc-testresults for confirmation.
best,
benjamin
> > Can you try
> >
> > int i;
> >
> > with "-Werror -ffunction-sections -fdata-sections" and see if
> > you get an
> > error with g++?
>
> With GNU C++ version 4.3.0 20070513 (experimental)
> (i686-pc-mingw32dw2)
> No error. i is put in its own section .data$i
But error when I add "-g" to
Weird. Does -std=c++0x or -std=gnu++0x make a difference?
I'm trying to figure out why I see this warning/error for things like
17_intro/headers/all_c++200x_compatibility.cc
but not always.
-benjamin
>
> libstdc++ configure is already probing to see if the target
> supports the
> use of this flag without errors. It thinks AIX and cygwin can
> use this
> flag without errors or warnings, which is clearly wrong.
>
> So, something needs to be fixed.
>
> Can you try
>
> int i;
>
> with "-W
[EMAIL PROTECTED] wrote:
cc1plus: warnings being treated as errors
/cygdrive/e/gnu/gcc-4.3-20070511/libstdc++-v3/testsuite/17_int
ro/headers/all_c++200x_compatibility.cc:1:
error: -ffunction-sections may affect debugging on some targets
This is actually a useful warning, since -ffunction-sec
This is actually a useful warning, since -ffunction-sections not only
affects debugging but also adds unnecessary size to executables on
PE-COFF targets (and others where ld does not support --gc-sections).
One way to avoid is to add --enable-cxx-flags='-fno-function-sections
-fno-data-sections
>
> cc1plus: warnings being treated as errors
>
> /cygdrive/e/gnu/gcc-4.3-20070511/libstdc++-v3/testsuite/17_int
> ro/headers/all_c++200x_compatibility.cc:1:
> error: -ffunction-sections may affect debugging on some targets
>
This is actually a useful warning, since -ffunction-sections not on
