[ clisp-Bugs-3485514 ] Cygwin & Pipes

Bugs item #3485514, was opened at 2012-02-07 14:46
Message generated for change (Comment added) made by toddcpierce
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3485514&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: build problems
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Todd Pierce (toddcpierce)
Assigned to: Bruno Haible (haible)
Summary: Cygwin & Pipes

Initial Comment:
Hello CLISP crew!

This is not really a bug.  After all, Cygwin just started supporting named pipes.  It appears, though, that the build of CLISP being distributed along with Cygwin doesn't recognize them.  The version of CLISP is this:

Welcome to GNU CLISP 2.48 (2009-07-28) 

Since CLISP is turrning out to be the most comfy place for my artificial intelligence to, well... think.

The behavior I noticed is that CLISP would just lock when trying to write to a pipe.  Writing to files works fine.  Reading from the pipe in another terminal window invoked an error in the CLISP session.

I'll mention this to the Cygwin guys too.  I just want you to be on the same page.

Thanks for all the help.

Sincerely, 

-Todd



----------------------------------------------------------------------

>Comment By: Todd Pierce (toddcpierce)
Date: 2013-03-30 10:27

Message:
Hi all, 

So, it looks like the Cygwin people fixed the pipes but then forgot to
include clisp in their distribution.

-Todd

----------------------------------------------------------------------

Comment By: Todd Pierce (toddcpierce)
Date: 2012-03-05 15:45

Message:
Crew:

Opening the file binary or not seems to cause the open file to lock.  Here
(the open hidden in my own function):

[2]> (setf stream (open-sparser "../stanford-parser/fifoin"))

locks the repl.  However, if I try to read from the other end of the pipe,
I do get this error (binary or not):

*** - UNIX error 22 (EINVAL): Invalid argument
The following restarts are available:
ABORT          :R1      Abort main loop

*** - UNIX error 11 (EWOULDBLOCK): Operation would block
The following restarts are available:
ABORT          :R1      Abort main loop

So, I'm not sure what is going on there.  I'm hoping I can just port my
whole project to a real unix system soon.  Whatever happens, I'll mention
this stuff to the cygwin guys.

Thanks for keeping an eye out for me.

-Todd

----------------------------------------------------------------------

Comment By: Todd Pierce (toddcpierce)
Date: 2012-02-08 15:49

Message:
This bug report is now marked as "pending"/"invalid".
This means that we think that the problem you report is not a problem with
CLISP.
Unless you - the reporter - act within 2 weeks, the bug will be permanently
closed.
Sorry about the inconvenience - we hope your silence means that you agree
that this is not a bug in CLISP.

----------------------------------------------------------------------

Comment By: Todd Pierce (toddcpierce)
Date: 2012-02-08 15:49

Message:
Someone mentioned that this could be a CRLF issue in the mailing list. 

This is not an issue that occurs when reading or writing to the pipe, this
is something that happens when opening it..  If you can even call Cygwin
having pipes yet.  

As I mentioned before, all the file open/close read/write happens fine. 
It's just when dealing with these new Cygwin pipes that things get
strange.

And no, I still haven't posted this matter with the Cygwin guys...  hell...
I'm homeless.

-Todd cambio y fuera

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2012-02-08 07:07

Message:
Todd: maybe you could try binary i/o with pipes? 

Reini: clisp accepts all 3 line terminators (cr, lf, crlf) on input, 
please see http://clisp.org/impnotes/clhs-newline.html

----------------------------------------------------------------------

Comment By: Reini Urban (rurban)
Date: 2012-02-07 17:34

Message:
Maybe because clisp upstream decided to read from pipes with crlf
line-endings, so \n will not end a line. Only the cygwin release reads from
pipes binary. Which makes more sense to cygwin, since we (cygwin) cannot
deal with crlf and we want to pipe streams with line endings to clisp.

Otherwise I see no difference but i haven't tested the new named pipes yet.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3485514&group_id=1355

------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel