I've attached the output of `cygcheck -s -v'. I'd ran the Cygwin setup
program this morning and was trying to build some Emacs Lisp files to get
my home directory in order--everything was downloaded from
<http://archive.progeny.com/cygwin/>, IIRC, as of about 12:00EST.
Oh--the shebang line in the script references /bin/sh. It was generated
by autoconf-2.53, if that's of any importance. `ls' is aliased to `ls -F',
but even when unaliased `configure' barfs. $CYGWIN is set to `tty notitle
glob ntsec'.
Your original post used "-L" ("-L, --dereference list entries pointed to
by symbolic links") not "-F" ("-F, --classify append indicator (one of
*/=@|) to entries").*Update* So to check that I'm not imagining things, I re-ran the set of
commands I'd put in the email, and now they're working correctly for me.
The configure script, however, still does not. I've attached the source
tarball that's failing--it's my Emacs startup files, please no comments on
the quality of my Lisp coding or overall incoherence of the files. :) If
you run:
$ tar xzvf bw-emacs-1.2.2.tar.gz
$ cd bw-emacs-1.2.2
$ ./configure
you should (?) get an error stating that `ls -t appears to fail'. The
associated lines are the ones mentioned in my initial post. I'll continue
rooting through the script to see what may be causing it, but if you have
any thoughts I'd appreciate hearing them.
Thanks!
-- mjb
> -----Original Message-----
> From: Randall R Schulz [mailto:rrschulz@cris.com]
> Sent: Wednesday, 2003 January 08 15:09
> To: cygwin@cygwin.com
> Subject: Re: Bash backquote bug?
>
>
> Michael,
>
> I cannot reproduce this. When I recreate your experiment, I
> get the results
> I'd expect.
>
> Are you sure your script is using BASH? You should know that
> /bin/sh is
> ash, not BASH. Nonetheless, I cannot reproduce the problem
> with ash, either.
>
> Out of curiosity, why are you using the "-L" option to "ls?"
> Are symbolic
> links involved here?
>
> Please send "cygcheck -s -v" output as a non-inline,
> non-compressed text
> attachment.
>
> Randall Schulz
>
>
> At 12:44 2003-01-08, Barillier, Michael wrote:
> >While running a configure script under bash-2.05b, I
> observed a bug (?)
> >similar to the following:
> >
> > $ ls configure*
> > configure configure.in
> > $ echo timestamp >conftest.file
> > $ ls -Lt ./configure conftest.file
> > conftest.file ./configure
> > $ set X `ls -Lt ./configure conftest.file`
> > $ echo $*
> > X conftest.file ./configure ./configure.in
> >
> >So, it appears that `ls' produces different output when
> evaluated at the
> >command prompt and when run under backquote. Any ideas?
> >
> >-- mjb