Mail Archives: cygwin/2002/07/23/19:16:33
One other thing: You might try using the alternative syntax for the
'expr' command, that is, instead of:
expr STRING : REGEXP
try
expr match STRING REGEXP
Specifically,
$ expr match xposixmutexes
'.*[^-_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789]'
should return 0 (zero).
> -----Original Message-----
> From: Harig, Mark A.
> Sent: Tuesday, July 23, 2002 7:09 PM
> To: Nicholas Wourms; cygwin AT cygwin DOT com
> Subject: RE: autoconf issues [often when upgrading from 2.13->2.53a]
>
>
> First some facts about what I have:
>
> 1. I have access to Win2K, but not 98/ME/etc.
>
> 2. cygwin, version 1.3.12-2
>
> 3. $ bash --version
> GNU bash, version 2.05a.0(3)-release (i686-pc-cygwin)
> Copyright 2001 Free Software Foundation, Inc.
>
> 4. $ expr --version
> expr (GNU sh-utils) 2.0
>
> Looking at the log of the configure session that you included, it's
> apparent that your version of 'expr' is returning the wrong result.
> Here's the command that the configure script runs:
>
> expr xposixmutexes :
> '.*[^-_abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ012
> 3456789]'
> && echo hello
>
> (I changed the 'echo' portion for simplicity.)
>
> This invocation of 'expr' should return 0 (zero) and the
> second half of
> the '&&' expression should not be evaluated, but on your system it is.
>
> You might try running the first half of the '&&' expression
> without the
> second half to see what position in the 'xposixmutexes' string 'expr'
> thinks it is finding an invalid character.
>
> Are you running the latest stable version of 'expr' that Cygwin has
> available? It's included in sh-utils 2.0-2, which is in the 'Base'
> category when setup.exe is run.
>
> >
> > I have attached a log of the configure session with set -xv. Don't
> > worry, it bombs out early, so it isn't that big. I'll do the same
> > procedure on win2k, if you want. The offending checkpoint is:
> >
> > -enable-* | --enable-*)
> > ac_feature=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'`
> > # Reject names that are not valid shell variable names.
> > expr "x$ac_feature" : ".*[^-_$as_cr_alnum]" >/dev/null &&
> > { echo "$as_me: error: invalid feature name: $ac_feature" >&2
> > { (exit 1); exit 1; }; }
> > ac_feature=`echo $ac_feature | sed 's/-/_/g'`
> > case $ac_option in
> > *=*) ac_optarg=`echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"`;;
> > *) ac_optarg=yes ;;
> > esac
> > eval "enable_$ac_feature='$ac_optarg'" ;;
> >
> > The options I'm passing are:
> >
> > CFLAGS=-O2 \
> > LDFLAGS= \
> > CC=gcc-2 \
> > CXX=g++-2 \
> > ../dist/configure --target=i686-pc-cygwin --prefix=/usr
> > --exec-prefix=/usr --sysconfdir=/etc --bindir=/usr/bin
> > --libdir=/usr/lib --includedir=/usr/include/db3.1
> > --datadir=/usr/share '--libexecdir=${sbindir}' --localstatedir=/var
> > '--program-transform-name=s,^db_,db3.1_,' --enable-posixmutexes
> > --enable-dynamic --enable-cxx --enable-compat185 --disable-test
> >
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
>
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -