← Back to branch summary

~drizzle-trunk/drizzle/development

« back to all changes in this revision

Viewing changes to BUILD/compile-pentium-valgrind-max

  • Committer: Stewart Smith
  • Date: 2008-06-29 23:41:16 UTC
  • mto: (12.3.1 drizzle-stew)
  • mto: This revision was merged to the branch mainline in revision 18.
  • Revision ID: stewart@flamingspork.com-20080629234116-4x3edz53t4gcf6cf
remove old BUILD/ that nobody uses (or it's broken). keep autorun.sh, because stewart is lazy and likes running it

Show diffs side-by-side

added added

removed removed

Lines of Context:
BUILD/compile-pentium-valgrind-max
1
 
#! /bin/sh
2
 
 
3
 
path=`dirname $0`
4
 
. "$path/SETUP.sh"
5
 
 
6
 
extra_flags="$pentium_cflags $debug_cflags $valgrind_flags"
7
 
extra_configs="$pentium_configs $debug_configs $max_configs"
8
 
 
9
 
. "$path/FINISH.sh"
10
 
 
11
 
if test -z "$just_print"
12
 
then
13
 
  set +v +x
14
 
  echo "\
15
 
******************************************************************************
16
 
Note that by default BUILD/compile-pentium-valgrind-max calls 'configure' with
17
 
--enable-assembler. When Valgrind detects an error involving an assembly
18
 
function (for example an uninitialized value used as an argument of an
19
 
assembly function), Valgrind will not print the stacktrace and 'valgrind
20
 
--gdb-attach=yes' will not work either. If you need a stacktrace in those
21
 
cases, you have to run BUILD/compile-pentium-valgrind-max with the
22
 
--disable-assembler argument.
23
 
******************************************************************************"
24
 
fi