delorie.com/archives/browse.cgi | search |
From: | tom DOT nurkkala AT powercerv DOT com ("Nurkkala, Tom") |
Subject: | Bash and "here files" |
3 Jan 1997 16:08:34 -0800 : | |
Sender: | daemon AT cygnus DOT com |
Approved: | cygnus DOT gnu-win32 AT cygnus DOT com |
Distribution: | cygnus |
Message-ID: | <c=US%a=_%p=powercerv%l=X1MSP01-970103222500Z-48453.cygnus.gnu-win32@x1msp01.powercerv.com> |
Original-To: | "'gnu-win32 AT cygnus DOT com'" <gnu-win32 AT cygnus DOT com> |
X-Mailer: | Microsoft Exchange Server Internet Mail Connector Version 4.0.993.5 |
Encoding: | 17 TEXT |
Original-Sender: | owner-gnu-win32 AT cygnus DOT com |
I've just downloaded the complete b17.1 release, and am running on NT 4.0 Workstation. I've tried to build several GNU executables, but can't get past 'configure'. In particular, bash seems to choke on the "here" files that output configure's test files. A simple example of this behavior follows: bash$ cat > foo1 << EOF > this is > a test > EOF bash.exe: 49060164: No such file or directory bash$ Any idea why this is occurring? thanks, nurk. - For help on using this list, send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |