Mail Archives: cygwin/1996/11/25/10:27:21
At 03:44 PM 11/24/96 -0500, Greg Rumple wrote:
>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 |
>|-----------------------------------------------------|
>
>
If this truly is not just a problem with a missing /tmp directory
(I don't know; I didn't try it), then it must be a b16 bug. I tried
the above example on the command line in b14 and it works just fine.
If its a b16 bug, maybe it will be fixed in b17???
Larry
-
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 -