s4-heimdal: disable using the system compile_et for now

just checking that compile_et exists isn't enough. It has to actually
work. Quite a few build farm systems have /usr/bin/compile_et, but it
gets link errors when you try to use it (missing symbols et_list_lock
and et_list_unlock)

Autobuild-User: Andrew Tridgell <tridge@samba.org>
Autobuild-Date: Wed Oct  6 07:48:16 UTC 2010 on sn-devel-104

diff --git a/source4/heimdal_build/wscript_configure b/source4/heimdal_build/wscript_configure
index e8f258ca460dbe2ac0ea4a686e845729df2e9462..78b0df506316e74e83065535827ef64706110a7d 100644 (file)
--- a/source4/heimdal_build/wscript_configure
+++ b/source4/heimdal_build/wscript_configure
@@ -63,5 +63,8 @@ conf.DEFINE('SAMBA4_INTERNAL_HEIMDAL', 1)
 if conf.CHECK_BUNDLED_SYSTEM('com_err', checkfunctions='com_right_r com_err', headers='com_err.h'):
     conf.define('USING_SYSTEM_COM_ERR', 1)
 
-if conf.find_program('compile_et', var='COMPILE_ET'):
-    conf.define('USING_SYSTEM_COMPILE_ET', 1)
+# disable trying to use an external compile_et until we have a configure
+# test that checks that the system one actually works. On some systems it
+# results in missing symbols (eg. OpenSUSE 10.2 'opi' in the build farm)
+#if conf.find_program('compile_et', var='COMPILE_ET'):
+#    conf.define('USING_SYSTEM_COMPILE_ET', 1)