X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_NUMERIC_HELO,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Achim Gratz Subject: Re: Maxima can't write to /dev/stdout Date: Thu, 26 Jul 2012 09:23:37 +0000 (UTC) Lines: 20 Message-ID: References: <20120726081722 DOT GA5132 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Corinna Vinschen cygwin.com> writes: > And here something goes wrong. If I call `echo foo > /dev/stdout' in > bash, the above normalize_posix_path calls already handle the path > /proc/196/fd/1, not just /proc/196/fd as lisp does. Thanks for having a look, that got me one step further. Maxima uses a (captive) clisp and the standalone clisp makes the same error: [1]> (open "/dev/stdout") *** - OPEN: File #P"/proc/3348/fd/" does not exist So the same thing happens in clisp and it seems to affect only(?) symlinks pointing to /proc, some other symlinks I tried that were pointing to /dev/tty as a test have not had that problem. Is it possible that clisp uses an API that isn't aware of /proc somehow? Regards, Achim -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple