cannam@125: dnl Copyright (C) 2013 Xiph.org Foundation cannam@125: dnl cannam@125: dnl Redistribution and use in source and binary forms, with or without cannam@125: dnl modification, are permitted provided that the following conditions cannam@125: dnl are met: cannam@125: dnl cannam@125: dnl - Redistributions of source code must retain the above copyright cannam@125: dnl notice, this list of conditions and the following disclaimer. cannam@125: dnl cannam@125: dnl - Redistributions in binary form must reproduce the above copyright cannam@125: dnl notice, this list of conditions and the following disclaimer in the cannam@125: dnl documentation and/or other materials provided with the distribution. cannam@125: dnl cannam@125: dnl - Neither the name of the Xiph.org Foundation nor the names of its cannam@125: dnl contributors may be used to endorse or promote products derived from cannam@125: dnl this software without specific prior written permission. cannam@125: dnl cannam@125: dnl THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS cannam@125: dnl ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT cannam@125: dnl LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR cannam@125: dnl A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR cannam@125: dnl CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, cannam@125: dnl EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, cannam@125: dnl PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR cannam@125: dnl PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF cannam@125: dnl LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING cannam@125: dnl NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS cannam@125: dnl SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. cannam@125: cannam@125: dnl Want to know of GCC stack protector works, botfor the C and for the C++ cannam@125: dnl compiler. cannam@125: dnl cannam@125: dnl Just checking if the compiler accepts the required CFLAGSs is not enough cannam@125: dnl because we have seen at least one instance where this check was cannam@125: dnl in-sufficient. cannam@125: dnl cannam@125: dnl Instead, try to compile and link a test program with the stack protector cannam@125: dnl flags. If that works, we use it. cannam@125: cannam@125: AC_DEFUN([XIPH_GCC_STACK_PROTECTOR], cannam@125: [AC_LANG_ASSERT(C) cannam@125: AC_MSG_CHECKING([if $CC supports stack smash protection]) cannam@125: xiph_stack_check_old_cflags="$CFLAGS" cannam@125: SSP_FLAGS="-fstack-protector --param ssp-buffer-size=4" cannam@125: CFLAGS=$SSP_FLAGS cannam@125: AC_TRY_LINK([ cannam@125: #include cannam@125: ], cannam@125: [puts("Hello, World!"); return 0;], cannam@125: AC_MSG_RESULT([yes]) cannam@125: CFLAGS="$xiph_stack_check_old_cflags $SSP_FLAGS", cannam@125: AC_MSG_RESULT([no]) cannam@125: CFLAGS="$xiph_stack_check_old_cflags" cannam@125: ) cannam@125: ])# XIPH_GCC_STACK_PROTECTOR cannam@125: cannam@125: AC_DEFUN([XIPH_GXX_STACK_PROTECTOR], cannam@125: [AC_LANG_PUSH([C++]) cannam@125: AC_MSG_CHECKING([if $CXX supports stack smash protection]) cannam@125: xiph_stack_check_old_cflags="$CFLAGS" cannam@125: SSP_FLAGS="-fstack-protector --param ssp-buffer-size=4" cannam@125: CFLAGS=$SSP_FLAGS cannam@125: AC_TRY_LINK([ cannam@125: #include cannam@125: ], cannam@125: [puts("Hello, World!"); return 0;], cannam@125: AC_MSG_RESULT([yes]) cannam@125: CFLAGS="$xiph_stack_check_old_cflags $SSP_FLAGS", cannam@125: AC_MSG_RESULT([no]) cannam@125: CFLAGS="$xiph_stack_check_old_cflags" cannam@125: ) cannam@125: AC_LANG_POP([C++]) cannam@125: ])# XIPH_GXX_STACK_PROTECTOR