Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: linux-gnu
Compiler: i386-pc-linux-gcc
Compilation 
CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu' 
-DCONF_MACHTYPE='i386-pc-linux-gnu' -DCONF_VENDOR='pc' 
-DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H 
-D_GNU_SOURCE   -I.  -I. -I./include -I./lib   -Os -march=i386 
-fno-strength-reduce
uname output: Linux upstairs 2.6.18 #4 SMP PREEMPT Sun Oct 8 15:44:22 UTC 2006 
i686 GNU/Linux
Machine Type: i386-pc-linux-gnu

Bash Version: 3.2
Patch Level: 0
Release Status: release

Description:
The configure script from kdelibs-3.5.5 can't be run under bash 3.2. It runs 
fine under bash 3.1. When I run the script I get:
        
[...snip...]
checking for MAXPATHLEN... ./configure: line 55636: syntax error near 
unexpected token `do'
./configure: line 55636: `  dirs=`for i in $files; do if test -d $i; then echo 
$i; fi; done`'
[...snip...]

I patch the script to get by this problem with this patch:

--- configure.orig      2006-10-13 14:07:06.000000000 +0000
+++ configure   2006-10-13 14:11:00.000000000 +0000
@@ -55633,9 +55633,10 @@

 if test ! -s $srcdir/subdirs; then
     files=`cd $srcdir && ls -1`
-  dirs=`for i in $files; do if test -d $i; then echo $i; fi; done`
-  for i in $dirs; do
-    echo $i >> $srcdir/subdirs
+ for i in $files; do
+    if test -d $i;
+      echo $i >> $srcdir/subdirs
+    fi
   done
 fi

But then I run into another failure:
[...snip...]
checking for MAXPATHLEN... ./configure: line 57125: syntax error near 
unexpected token `('
./configure: line 57125: `    case `(ac_space=' '; set | grep ac_space) 2>&1` 
in'
[...snip...]

I've now reverted to bash 3.1 but can switch back at any time to help test any 
fixes.

Repeat-By:

Unpack the kdelibs-3.5.5 tarball, cd into the top source directory and run 
configure.

Fix:

Sorry, that's little beyond my capabilities :)


_______________________________________________
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash

Reply via email to