2002-10-29 21:59:03 +02:00
|
|
|
#! /bin/sh
|
|
|
|
|
|
|
|
path=`dirname $0`
|
2006-04-07 02:25:59 +04:00
|
|
|
. "$path/SETUP.sh" "$@"
|
2002-10-29 21:59:03 +02:00
|
|
|
|
2006-04-05 16:50:12 +04:00
|
|
|
extra_flags="$pentium_cflags $debug_cflags $valgrind_flags"
|
|
|
|
extra_configs="$pentium_configs $debug_configs $max_configs"
|
2002-10-29 21:59:03 +02:00
|
|
|
|
|
|
|
. "$path/FINISH.sh"
|
2003-09-30 00:08:12 +02:00
|
|
|
|
2003-10-08 21:50:05 +03:00
|
|
|
if test -z "$just_print"
|
|
|
|
then
|
2003-11-04 14:59:38 +02:00
|
|
|
set +v +x
|
2003-10-08 21:50:05 +03:00
|
|
|
echo "\
|
|
|
|
******************************************************************************
|
2003-09-30 00:08:12 +02:00
|
|
|
Note that by default BUILD/compile-pentium-valgrind-max calls 'configure' with
|
|
|
|
--enable-assembler. When Valgrind detects an error involving an assembly
|
2003-10-08 21:50:05 +03:00
|
|
|
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
|