Displaying 4 results from an estimated 4 matches for "enable_flags_set".
2017 Jan 15
0
[PATCH 1/2] Do not override CFLAGS, as CFLAGS is a user flag.
...ether configure should try to set CFLAGS/CXXFLAGS/CPPFLAGS/LDFLAGS])
+AS_IF([test "x${CFLAGS+set}" = "xset" || test "x${CXXFLAGS+set}" = "xset" || test "x${CPPFLAGS+set}" = "xset" || test "x${LDFLAGS+set}" = "xset"],
+ [enable_flags_setting=no],
+ [enable_flags_setting=yes]
+)
+AC_MSG_RESULT([${enable_flags_setting}])
+AX_CHECK_ENABLE_DEBUG
user_cflags=$CFLAGS
#Prefer whatever the current ISO standard is.
@@ -206,14 +213,7 @@ AC_DEFINE(FLAC__ALIGN_MALLOC_DATA)
AH_TEMPLATE(FLAC__ALIGN_MALLOC_DATA, [define to align allocated me...
2017 Jan 15
4
Updated CFLAGS patches and make test compilation conditional
Hi Erik,
I've found a middleground for the problem of setting default CFLAGS. I've gone back
to setting them if {C,CXX,CPP,LD}FLAGS are unset at the onset of the configure script
(i.e., the user hasn't specified anything) and then proceed to set them to the defaults
as before. This has been suggested before:
https://lists.gnu.org/archive/html/autoconf/2006-04/msg00022.html
In
2017 Feb 04
0
[PATCH] Clean up CFLAGS detecting code and add AX macro for _FORTIFY_SOURCE
...x 8576cae5..c5b63370 100644
--- a/configure.ac
+++ b/configure.ac
@@ -393,9 +393,7 @@ fi
dnl If debugging is disabled AND no CFLAGS/CXXFLAGS/CPPFLAGS/LDFLAGS
dnl are provided, we can set defaults to our liking
AS_IF([test "x${ax_enable_debug}" = "xno" && test "x${enable_flags_setting}" = "xyes"], [
- AC_PROG_SED
- CFLAGS=$(echo "$CFLAGS" | $SED 's/-O2//')
- CFLAGS="-O3 -funroll-loops $CFLAGS"
+ CFLAGS="-O3 -funroll-loops"
])
XIPH_GCC_VERSION
@@ -409,24 +407,7 @@ if test x$ac_cv_c_compiler_gnu = xyes ; then
dnl some...
2017 Feb 04
3
Minor CFLAGS-related cleanups
Hi Erik,
similar to what I did for libsndfile, this is to simplify the
handling of adding -D_FORTIFY_SOURCE=2.
Regards
David