From:	wrichard AT direct DOT ca (Wade Richards)
Subject:	RE: Strange configuration script problems...
24 Nov 1996 13:58:20 -0800 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<1.5.4.32.19961124202630.00687f50.cygnus.gnu-win32@mail.direct.ca>
Mime-Version:	1.0
X-Sender:	wrichard AT mail DOT direct DOT ca
X-Mailer:	Windows Eudora Light Version 1.5.4 (32)
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>
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

At 11:08 23/11/96 -0000, 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

The problem is quite simple.  Bash wants to create the in-line file in /tmp.
You don't have a directory /tmp.  Therefore bash fails.

Either create a directory c:\tmp, or use mount to map /tmp to some other
directory.  Test that the directory exists by executing "echo foo >
/tmp/foo.txt; cat /tmp/foo.txt" from Bash.
Note that many UNIX based programs will assume /tmp exists, this isn't a
bash-specific thing.

        --- Wade
----------
Wade Richards    -= WRichard AT Direct DOT CA =- 
"Never attribute to malice what can adequately be explained by stupidity."

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

- Raw text -