From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20585 invoked by alias); 26 Jul 2012 09:24:17 -0000 Received: (qmail 20571 invoked by uid 22791); 26 Jul 2012 09:24:15 -0000 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 Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 26 Jul 2012 09:23:49 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SuKIN-0008R6-AB for cygwin@cygwin.com; Thu, 26 Jul 2012 11:23:47 +0200 Received: from 217.10.60.85 ([217.10.60.85]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 26 Jul 2012 11:23:47 +0200 Received: from Stromeko by 217.10.60.85 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 26 Jul 2012 11:23:47 +0200 To: cygwin@cygwin.com From: Achim Gratz Subject: Re: Maxima can't write to /dev/stdout Date: Thu, 26 Jul 2012 09:24:00 -0000 Message-ID: References: <20120726081722.GA5132@calimero.vinschen.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@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-07/txt/msg00573.txt.bz2 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