summaryrefslogtreecommitdiff
path: root/build/make/configure.sh
diff options
context:
space:
mode:
authorYunqing Wang <yunqingwang@google.com>2012-10-24 09:14:36 -0700
committerYunqing Wang <yunqingwang@google.com>2012-10-24 09:22:10 -0700
commitbc1d3cb90bc17b03597b5c6dbcad896585ca4a8d (patch)
tree4a2b27b0c99da4a6a82a66da1f20066b10e3e8dc /build/make/configure.sh
parentedf099d27218b5f3dbd1c72fe20488dd24b638d2 (diff)
downloadlibvpx-bc1d3cb90bc17b03597b5c6dbcad896585ca4a8d.tar
libvpx-bc1d3cb90bc17b03597b5c6dbcad896585ca4a8d.tar.gz
libvpx-bc1d3cb90bc17b03597b5c6dbcad896585ca4a8d.tar.bz2
libvpx-bc1d3cb90bc17b03597b5c6dbcad896585ca4a8d.zip
Fix "_FORTIFY_SOURCE" redefined warning
On Ubuntu 12.04, we got the following warning message: <command-line>:0:0: warning: "_FORTIFY_SOURCE" redefined [enabled by default] <built-in>:0:0: note: this is the location of the previous definition This was already fixed in VP8 configure file. Did the same change in experimental branch to stop this warning. Change-Id: Id162e5fd8841585ae806df6560b2f7536ea307c0
Diffstat (limited to 'build/make/configure.sh')
-rwxr-xr-xbuild/make/configure.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/build/make/configure.sh b/build/make/configure.sh
index 9bff9cb22..00c27c261 100755
--- a/build/make/configure.sh
+++ b/build/make/configure.sh
@@ -974,7 +974,7 @@ process_common_toolchain() {
# Work around longjmp interception on glibc >= 2.11, to improve binary
# compatibility. See http://code.google.com/p/webm/issues/detail?id=166
- enabled linux && check_add_cflags -D_FORTIFY_SOURCE=0
+ enabled linux && check_add_cflags -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0
# Check for strip utility variant
${STRIP} -V 2>/dev/null | grep GNU >/dev/null && enable gnu_strip