Bug #9131 Configure fails looking for ORBit

• Submitted: 11 Mar 2005 18:30
• Modified: 1 Jul 2005 1:17
• Reporter: Claire McLister
• Status: Won't fix
• Category: MySQL Server: Compiling
• Severity: S3 (Non-critical)
• Version: 4.1.10
• OS: MacOS (MacOS)
• Assigned to: Kent Boortz
• CPU Architecture: Any

[11 Mar 2005 18:30] Claire McLister

Description:
When I ran ./configure on a downloaded tarball of 4.1.10, I get the following error message:

checking for ORBit... ./configure: line 1: orbit-config: command not found
./configure: line 1: orbit-config: command not found
./configure: line 1: orbit-config: command not found
found!

How to repeat:
Run configure on a tarball of 4.1.10 on Mac OS X, where orbit-config command is missing on the machine

Suggested fix:
This seems to be getting caused by the 'which' command returning the error
stream as part of its return value. This bug can be fixed by applying the following
patch to acinclude.m4

--- acinclude.m4.orig   Fri Mar 11 10:26:29 2005
+++ acinclude.m4        Fri Mar 11 10:27:11 2005
@@ -1096,7 +1096,7 @@
 
 AC_DEFUN([MYSQL_CHECK_ORBIT], [
 AC_MSG_CHECKING(for ORBit)
-orbit_config_path=`which orbit-config`
+orbit_config_path=`which orbit-config 2>/dev/null`
 if test -n "$orbit_config_path" -a $? = 0
 then
   orbit_exec_prefix=`orbit-config --exec-prefix`

or the following patch to configure:

--- configure.orig      Fri Mar 11 10:27:47 2005
+++ configure   Fri Mar 11 10:19:57 2005
@@ -36442,7 +36442,7 @@
 
 echo "$as_me:$LINENO: checking for ORBit" >&5
 echo $ECHO_N "checking for ORBit... $ECHO_C" >&6
-orbit_config_path=`which orbit-config`
+orbit_config_path=`which orbit-config 2>/dev/null`
 if test -n "$orbit_config_path" -a $? = 0
 then
   orbit_exec_prefix=`orbit-config --exec-prefix`

[11 Mar 2005 21:19] Claire McLister

The fix that I suggested earlier, actually does not work. Here's another one that does
seem to work:

--- configure.orig      Fri Mar 11 11:24:08 2005
+++ configure   Fri Mar 11 11:24:19 2005
@@ -36443,7 +36443,7 @@
 echo "$as_me:$LINENO: checking for ORBit" >&5
 echo $ECHO_N "checking for ORBit... $ECHO_C" >&6
 orbit_config_path=`which orbit-config`
-if test -n "$orbit_config_path" -a $? = 0
+if test -a "$orbit_config_path" -a $? = 0
 then
   orbit_exec_prefix=`orbit-config --exec-prefix`
   orbit_includes=`orbit-config --cflags server`

[14 Mar 2005 11:35] Kent Boortz

This is a cosmetic bug, but should be corrected. The test is about
sqlfs, that is not included, and it is unclear if we need to support it
any longer in our configure script. If still to be supported, the correct
patch is to find the path using "which", check that the string is not
empty, and check that the path exists. For strange reasons, at
least some "which" commands write their error message to stdout.

[1 Jul 2005 1:17] Brian Aker

We no longer support sqlfs.