mirror of
https://github.com/MariaDB/server.git
synced 2025-01-15 19:42:28 +01:00
25 lines
870 B
Text
25 lines
870 B
Text
|
#! /bin/sh
|
||
|
|
|
||
|
|
path=`dirname $0`
|
||
|
|
. "$path/SETUP.sh"
|
||
|
|
|
||
|
|
extra_flags="$amd64_cflags $debug_cflags $valgrind_flags"
|
||
|
|
extra_configs="$amd64_configs $debug_configs $max_configs"
|
||
|
|
|
||
|
|
. "$path/FINISH.sh"
|
||
|
|
|
||
|
|
if test -z "$just_print"
|
||
|
|
then
|
||
|
|
set +v +x
|
||
|
|
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
|