From: grumple AT magg DOT net (Greg Rumple)
Subject: RE: Strange configuration script problems...
24 Nov 1996 15:01:44 -0800
Sender: daemon AT cygnus DOT com
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <Pine.LNX.3.95.961124154256.6807A-100000.cygnus.gnu-win32@grumpy.magg.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Original-To: Warren & SLS Knight <knight AT dircon DOT co DOT uk>
Original-cc: "Gnu-win32 AT cygnus DOT com" <Gnu-win32 AT cygnus DOT com>
In-Reply-To: <01BBD92F.09A32E00@knight.dircon.co.uk>
Original-Sender: owner-gnu-win32 AT cygnus DOT com

On Sat, 23 Nov 1996, Warren & SLS Knight wrote:

> The problem appears to be with how the BASH shell handles the
> the << operator.  You will see what I mean if you try the following 
> in bash:
>   bash$ cat <<EOF 
>   > This is a test
>   > EOF
>   BASH.EXE: 9146372: No such file or directory
> 
> I have downloaded the source and am getting ready to look for 
> the error.  But I am new to this list and don't know if a patch has
> already been given.

You are correct, that hits the problem directly on the nose.  I have seen
quite a few discussions of this problem on this list, but no one has yet
come up with a fix, or a work around (besides re-writing the configure
script).

But if anyone does have a fix for this, I would like to get a copy of it.

|-----------------------------------------------------|
|  Greg Rumple                     grumple AT magg DOT net   |
|                                                     |
|  M.A.G. Information Services System Administrator   |
|                                                     |
| http://www.magg.net  South Florida's I-Net Provider |
|  (561) 964-9841           Accounts from 19.95       |
|-----------------------------------------------------|


-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".