Displaying 5 results from an estimated 5 matches for "xiph_add_cxxflags".
Did you mean:
xiph_add_cflags
2017 Feb 04
0
[PATCH] Clean up CFLAGS detecting code and add AX macro for _FORTIFY_SOURCE
...CE(
- [[
- int main() {
- #ifndef _FORTIFY_SOURCE
- return 0;
- #else
- this_is_an_error;
- #endif
- }
- ]]
- )], [
- AC_MSG_RESULT([yes])
- XIPH_ADD_CFLAGS([-D_FORTIFY_SOURCE=2])
- ], [
- AC_MSG_RESULT([no])
- ])
+ AX_ADD_FORTIFY_SOURCE
AC_LANG_PUSH([C++])
XIPH_ADD_CXXFLAGS([-Weffc++])
diff --git a/m4/ax_add_fortify_source.m4 b/m4/ax_add_fortify_source.m4
new file mode 100644
index 00000000..d443814b
--- /dev/null
+++ b/m4/ax_add_fortify_source.m4
@@ -0,0 +1,53 @@
+# ===========================================================================
+# http://www.gnu.org/so...
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
2013 Nov 20
4
[PATCH 1/2] Revert "configure.ac : If gcc is version 4.2, use -fgnu89-inline."
This reverts commit 2860f1780ca92c779ee0a2c545ae1b9c4818dc53.
Conflicts:
configure.ac
Do not use -fgnu89-inline as it can emit duplicate symbols for
inline functions that are declared in multiple object files
being linked together.
For example on clang 5.0 targetting iOS
(clang advertises itself as gcc 4.2, the last GPL version of gcc)
---
configure.ac | 12 ++++--------
1 file changed, 4
2017 Jan 15
0
[PATCH 1/2] Do not override CFLAGS, as CFLAGS is a user flag.
...IFELSE([
+ AC_LANG_SOURCE(
+ [[
+ int main() {
+ #ifndef _FORTIFY_SOURCE
+ return 0;
+ #else
+ this_is_an_error;
+ #endif
+ }
+ ]]
+ )], [
+ AC_MSG_RESULT([yes])
+ XIPH_ADD_CFLAGS([-D_FORTIFY_SOURCE=2])
+ ], [
+ AC_MSG_RESULT([no])
+ ])
AC_LANG_PUSH([C++])
XIPH_ADD_CXXFLAGS([-Weffc++])
diff --git a/include/FLAC/assert.h b/include/FLAC/assert.h
index b546fd07..55b34777 100644
--- a/include/FLAC/assert.h
+++ b/include/FLAC/assert.h
@@ -34,7 +34,7 @@
#define FLAC__ASSERT_H
/* we need this since some compilers (like MSVC) leave assert()s on release code (and we don...
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