Date: Tue, 22 Aug 2000 09:55:31 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: tr AT eth DOT net
Message-Id: <2427-Tue22Aug2000095531+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b
CC: djgpp-workers AT delorie DOT com, snowball3 AT bigfoot DOT com
In-reply-to: <200008220358.JAA01049@midpec.com> (message from Prashant TR on
	Tue, 22 Aug 2000 09:28:24 +0530)
Subject: Re: Problems with depcomp from fileutils 4.0x & bash 2.03
References: <39987229 DOT 2CB876B3 AT phekda DOT freeserve DOT co DOT uk> (message from Richard	Dawe on Mon, 14 Aug 2000 23:26:49 +0100) <3999297F DOT 23816 DOT 95FCA AT localhost> <200008201249 DOT SAA01237 AT midpec DOT com> <3099-Sun20Aug2000190425+0300-eliz AT is DOT elta DOT co DOT il> <200008220358 DOT JAA01049 AT midpec DOT com>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Date: Tue, 22 Aug 2000 09:28:24 +0530
> From: Prashant TR <tr AT eth DOT net>
> 
> There's a huge difference between these two files. After trying the
> new files from Juan, I again got the same error. Surprisingly, it
> compiles under Windows.

From what I see, Bash 2.04 has some trouble with any fragment of the
configure script which uses <<\EOF, like this:

    cat >$CONFIG_STATUS <<\EOF
    #! /bin/sh
    # Generated automatically by configure.
    # Run this file to recreate the current configuration.
    # Compiler output produced by configure, useful for debugging
    # configure, is in ./config.log if it exists.

    debug=false
    me=`echo "$0" | sed -e 's,.*/,,'`
    SHELL=${CONFIG_SHELL-/bin/sh}

    EOF

Each fragment that begins with "cat >$CONFIG_STATUS <<\EOF" disappears
from config.status produced by Bash 2.04!  "<<EOF", without a
backslash, doesn't cause this problem.

Mark, does that help to identify the problem?  Perhaps it is related
to the bugfixes related to backslashes you mentioned in another mail?