Bugs item #3485514, was opened at 2012-02-07 14:46
Message generated for change (Tracker Item Submitted) 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
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3485514&group_id=1355