Date: Thu, 23 Sep 1999 10:45:14 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: pavenis AT lanet DOT lv
cc: Davin McCall <DavMac AT iname DOT com>, djgpp AT delorie DOT com
Subject: Re: Compiling GCC
In-Reply-To: <B0000102732@stargate.astr.lu.lv>
Message-ID: <Pine.SUN.3.91.990923104155.10652E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 22 Sep 1999 pavenis AT lanet DOT lv wrote:

> > djconfig.log's first line reads:
> > 
> > c:/djgpp/bin/sed.exe: -e expression #2, char 1: Unknown command: ``.''
> > 
> > Maybe this is the problem?
> > 
> 
> It seems to be due bug in DJGPP port of bash-1.14.7 (result depends 
> on length of name of directory where gcc sources are unpacked, mor 
> exactly perhaps length of full patch:
> 	c:/tmp/x/   - problem was there
>        c:/tmp/xxxxxxxx/  - no problem

Bash does some special magic for Sed, because the automatic 
transformation of the //x/foo form of the DOS file names can misfire if 
it is actually a Sed script that uses slashes.  Perhaps this is what 
causes Bash to fail in this case.

One more proof that //x/foo is not such a good idea, if you ask me.