X-Authentication-Warning: new-smtp1.ihug.com.au: Host p205-tnt6.syd.ihug.com.au [203.173.146.205] claimed to be acceleron
Message-ID: <000b01c133a0$64f27600$0a02a8c0@acceleron>
From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To: "Mark E." <snowball3 AT bigfoot DOT com>,
        "Charles Sandmann" <sandmann AT clio DOT rice DOT edu>
Cc: <djgpp-workers AT delorie DOT com>
References: <001201c132bf$c3422980$0a02a8c0 AT acceleron> <004801c13365$01e25c50$0a02a8c0 AT acceleron>
Subject: Re: Bash 2.05 beta of 28-Aug-2001 query
Date: Sun, 2 Sep 2001 21:14:10 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Reply-To: djgpp-workers AT delorie DOT com

Mark,

I just downloaded the latest BASH 2.05 sources about an hour ago and re-ran
the test script below with the new bash.exe. I couldn't easily spot any
changes with regards to the issues below. They still appear to be there.

Any ideas?

Andrew
> > Mark,
> >
> > I have been trying to build GCC 2.95.2 from sources on Win 98 since the
> Bash
> > source relase of 28-Aug-2001 which fixed Bash crashing on Win2K. I have
> not
> > gotten to the bottom of the real issue outlined below as I cannot see
> where
> > to start (I will keep looking for another few hours), but if I go back
to
> > Bash 2.04 (only bash.exe changed) I can build GCC on Win 98.
> >
> > When I go into the GCC build.djg directory and run the follwoing command
> and
> > I find that the makefile, config.status and config,cache files are
> different
> > when I compare the resulting files from using Bash 2.04 and 2.05.
> >     redir -eo bash ./djbuild1.sh config >djconfig.log
> >
> > I tried to compare Bash 2.04 and Bash 2.05 source changes to see if I
> could
> > see where the problem may be, but there were too many changes for me to
> see
> > what may be the cause.
> >
> > Any ideas about what to do about this issue?
> >
> > Andrew
>
> The following very simple shell script also exhibits the same problem as
> with GCC:
>
> #! /bin/sh
> # Test Script for Bash 2.04 V's 2.05 usage
> ac_cv_prog_LN_S="cp -p"
> echo ${BASH_VERSION} > out.txt
> echo $ac_cv_prog_LN_S >>out.txt
>
> (set) 2>&1 |
>   case `(ac_space=' '; set | grep ac_space) 2>&1` in
>   *)
>     # `set' quotes correctly as required by POSIX, so do not add quotes.
>     sed -n -e 's/^\([a-zA-Z0-9_]*_cv_[a-zA-Z0-9_]*\)=\(.*\)/\1=${\1=\2}/p'
> #    less
>     ;;
>   esac >> out.txt
>
>
> BASH 2.04 sed output:
> ac_cv_prog_LN_S='cp -p'
>
> BASH 2.05 sed output:
> ac_cv_prog_LN_S=$'cp -p'
>
>
> If I use less instead of sed the info passed looke like the environemtn
> varaiables, but with Bash 2.05 some of the lines have the $ in then.
>
> Bash 2.04 less example:
> OSTYPE=msdosdjgpp
> PATH='C:/DJ204/BIN;C:/WINDOWS;C:/WINDOWS/COMMAND;C:/BIN'
>
> Bash 2.05 less example:
> OSTYPE=msdosdjgpp
> PATH=$'c:/dj204/bin;c:/windows;c:/windows/command;c:/bin'
>
> Andrew
>
>