From f972dce2a22525fa041f7df46af222235d03a7cb Mon Sep 17 00:00:00 2001
From: Davi Arnaut <davi@mysql.com>
Date: Tue, 27 May 2008 12:35:35 -0300
Subject: [PATCH] Add variation of compile-pentium-valgrind-max which does not
 build ndb.

BUILD/compile-pentium-valgrind-max-no-ndb:
  Disable ndb.
---
 BUILD/compile-pentium-valgrind-max-no-ndb | 24 +++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100755 BUILD/compile-pentium-valgrind-max-no-ndb

diff --git a/BUILD/compile-pentium-valgrind-max-no-ndb b/BUILD/compile-pentium-valgrind-max-no-ndb
new file mode 100755
index 00000000000..66f6ae08a7f
--- /dev/null
+++ b/BUILD/compile-pentium-valgrind-max-no-ndb
@@ -0,0 +1,24 @@
+#! /bin/sh
+
+path=`dirname $0`
+. "$path/SETUP.sh"
+
+extra_flags="$pentium_cflags $debug_cflags $valgrind_flags"
+extra_configs="$pentium_configs $debug_configs $max_no_ndb_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