#44 failed ./configure for tclx8.4

[Kalin KOZHUHAROV]

Trying to build tclx8.4 I cannot go past ./configure.
I have tcl-8.4.12 and tk-8.4.12, downloaded and
unpacked tclx84.tar.bz2 ... Then:

tclx8.4 # ./configure --disable-threads
checking for correct TEA configuration... ok (TEA 3.3)
checking for Tcl configuration... found
/usr/lib/tclConfig.sh
checking for existence of /usr/lib/tclConfig.sh... loading
configure: --prefix defaulting to TCL_PREFIX /usr
configure: --exec-prefix defaulting to TCL_EXEC_PREFIX /usr
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... gcc -E
checking for a BSD-compatible install...
/usr/bin/install -c
checking whether make sets $(MAKE)... yes
checking for ranlib... ranlib
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking if the compiler understands -pipe... yes
checking whether byte ordering is bigendian... no
checking for sin... no
checking for main in -lieee... yes
checking for main in -linet... no
checking net/errno.h usability... no
checking net/errno.h presence... no
checking for net/errno.h... no
checking for connect... yes
checking for gethostbyname... yes
checking dirent.h...
checking errno.h usability... yes
checking errno.h presence... yes
checking for errno.h... yes
checking float.h usability... yes
checking float.h presence... yes
checking for float.h... yes
checking values.h usability... yes
checking values.h presence... yes
checking for values.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/wait.h usability... yes
checking sys/wait.h presence... yes
checking for sys/wait.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking for Tcl private include files... Using srcdir
found in tclConfig.sh: /usr/lib/tcl8.4/include
checking for building with threads... no
checking how to build libraries... shared
checking for tclsh... /usr/bin/tclsh8.4
checking if 64bit support is enabled... no
checking if 64bit Sparc VIS support is requested... no
checking system version (for dynamic loading)...
./configure: line 13965: syntax error near unexpected
token `ac_space=' ''
./configure: line 13965: ` case `(ac_space=' '; set
| grep ac_space) 2>&1` in'

That is with:
GNU bash, version 3.1.10(1)-release (i686-pc-linux-gnu)

--enable-threads fails in the same spot

Anyhing other info I can provide?

[Nobody/Anonymous]

Logged In: NO

I have been struggling with the same issue on Fedora Core 5
install.

GNU bash, version 3.1.7(1)-release (i386-redhat-linux-gnu)

[Nobody/Anonymous]

Logged In: NO

Obvious workaround, compile a copy of bash 3.0 on the system
and alter the first line of configure to point to that
rather than /bin/sh

[Nobody/Anonymous]

Logged In: NO

I'm getting the same error on a Gentoo system with the following output from /bin/bash --version:

GNU bash, version 3.1.16(1)-release (x86_64-pc-linux-gnu)

This is an AMD64 architecture machine. I get the same error with or without the --enable-64bit option to configure.

Can someone suggest an appropriate modification to get the configure script to complete? I have also tried changing the #!/bin/sh to #!/bin/bash, with no change in results. I would expect there is some really easy workaround for a configure / shell script expert (not me!)...