From: tvaughan AT redwood DOT dn DOT hac DOT com (Thomas Vaughan)
Subject: GNU-Win32 17.1, NT 4.0, and BASH hereis (<<) document
11 Apr 1997 14:23:17 -0700
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <199704111644.KAA08547.cygnus.gnu-win32@extreme.dn.hac.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Original-To: gnu-win32 AT cygnus DOT com
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
Original-Sender: owner-gnu-win32 AT cygnus DOT com


I have read the FAQ and perused the mailing list archive, but I have not
found an answer to a strange problem that I have with BASH.  After a
complete failure to a configure script for one of the GNU utilities, I
traced the problem to the hereis document feature of BASH.  Below is an
example transcript.

   bash$ echo > test <<pig
   > cow
   > chicken
   > pig
   BASH.EXE: 49082020: No such file or directory
   bash$

This is a serious problem, because just about all GNU configure scripts use
this BASH feature.  A friend of mine who installed GNU-Win32 in almost
exactly the same way on his NT 3.51 machine has no such problem with BASH.
I have reinstalled twice now with the same results each time.

Any help would be greatly appreciated.

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