mirror of
https://github.com/MariaDB/server.git
synced 2025-01-23 23:34:34 +01:00
27 lines
1.1 KiB
Bash
Executable file
27 lines
1.1 KiB
Bash
Executable file
#! /bin/sh
|
|
|
|
path=`dirname $0`
|
|
. "$path/SETUP.sh"
|
|
|
|
extra_flags="$pentium_cflags $debug_cflags -USAFEMALLOC -UFORCE_INIT_OF_VARS -DHAVE_purify"
|
|
c_warnings="$c_warnings $debug_extra_warnings"
|
|
cxx_warnings="$cxx_warnings $debug_extra_warnings"
|
|
extra_configs="$pentium_configs $debug_configs"
|
|
|
|
extra_configs="$extra_configs --with-berkeley-db --with-innodb --without-isam --with-embedded-server --with-openssl"
|
|
|
|
. "$path/FINISH.sh"
|
|
|
|
if test -z "$just_print"
|
|
then
|
|
echo "\
|
|
******************************************************************************
|
|
Note that by default BUILD/compile-pentium-valgrind-max calls 'configure' with
|
|
--enable-assembler. When Valgrind detects an error involving an assembly
|
|
function (for example an uninitialized value used as an argument of an
|
|
assembly function), Valgrind will not print the stacktrace and 'valgrind
|
|
--gdb-attach=yes' will not work either. If you need a stacktrace in those
|
|
cases, you have to run BUILD/compile-pentium-valgrind-max with the
|
|
--disable-assembler argument.
|
|
******************************************************************************"
|
|
fi
|