summaryrefslogtreecommitdiffstats
path: root/config/gnu-flags
diff options
context:
space:
mode:
authorQuincey Koziol <koziol@hdfgroup.org>2011-04-20 16:17:08 (GMT)
committerQuincey Koziol <koziol@hdfgroup.org>2011-04-20 16:17:08 (GMT)
commit4f17c3c59197ac215880ad168b040bec6b48092b (patch)
treeb097c964e900ccde29ddf15315f59f7339cbdc96 /config/gnu-flags
parent697ca4c4fe283054eb44cae5ab9623d72deb392d (diff)
downloadhdf5-4f17c3c59197ac215880ad168b040bec6b48092b.zip
hdf5-4f17c3c59197ac215880ad168b040bec6b48092b.tar.gz
hdf5-4f17c3c59197ac215880ad168b040bec6b48092b.tar.bz2
[svn-r20562] Description:
Bring r20561 from trunk to 1.8 branch: Remove C++ specific flag from C compilation flags, for gcc 4.5 & 4.6 Tested on: FreebSD/64 8.2 (freedom) w/gcc 4.6
Diffstat (limited to 'config/gnu-flags')
-rw-r--r--config/gnu-flags4
1 files changed, 2 insertions, 2 deletions
diff --git a/config/gnu-flags b/config/gnu-flags
index 2ef29e5..1222c87 100644
--- a/config/gnu-flags
+++ b/config/gnu-flags
@@ -236,7 +236,7 @@ case "$cc_vendor-$cc_version" in
H5_CFLAGS="$H5_CFLAGS -Wsync-nand -Wframe-larger-than=16384 -Wpacked-bitfield-compat"
# Append more extra warning flags that only gcc 4.5+ know about
- H5_CFLAGS="$H5_CFLAGS -Wstrict-aliasing -Wstrict-overflow=5 -Wc++0x-compat -Wjump-misses-init -Wunsuffixed-float-constants"
+ H5_CFLAGS="$H5_CFLAGS -Wstrict-aliasing -Wstrict-overflow=5 -Wjump-misses-init -Wunsuffixed-float-constants"
# Append more extra warning flags that only gcc 4.6+ know about
H5_CFLAGS="$H5_CFLAGS -Wdouble-promotion -Wsuggest-attribute=const -Wtrampolines"
@@ -300,7 +300,7 @@ case "$cc_vendor-$cc_version" in
H5_CFLAGS="$H5_CFLAGS -Wsync-nand -Wframe-larger-than=16384 -Wpacked-bitfield-compat"
# Append more extra warning flags that only gcc 4.5+ know about
- H5_CFLAGS="$H5_CFLAGS -Wstrict-aliasing -Wstrict-overflow=5 -Wc++0x-compat -Wjump-misses-init -Wunsuffixed-float-constants"
+ H5_CFLAGS="$H5_CFLAGS -Wstrict-aliasing -Wstrict-overflow=5 -Wjump-misses-init -Wunsuffixed-float-constants"
# Try out the new "stack protector" feature in gcc 4.1
# (Strictly speaking this isn't really a "warning" flag, so it's added to