From: Achim Gratz <Stromeko@NexGo.DE>
To: cygwin@cygwin.com
Subject: Re: Maxima can't write to /dev/stdout
Date: Thu, 26 Jul 2012 09:24:00 -0000 [thread overview]
Message-ID: <loom.20120726T110441-843@post.gmane.org> (raw)
In-Reply-To: <20120726081722.GA5132@calimero.vinschen.de>
Corinna Vinschen <corinna-cygwin <at> 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
next prev parent reply other threads:[~2012-07-26 9:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 7:05 Achim Gratz
2012-07-26 8:18 ` Corinna Vinschen
2012-07-26 8:46 ` Corinna Vinschen
2012-07-26 9:24 ` Achim Gratz [this message]
2012-07-26 9:47 ` Corinna Vinschen
2012-07-26 13:21 ` Earnie Boyd
2012-07-26 17:57 ` Achim Gratz
2012-07-26 18:57 ` Reini Urban
2012-07-26 19:11 ` Achim Gratz
2012-07-26 19:36 ` Reini Urban
2012-07-27 1:54 ` Yaakov (Cygwin/X)
2012-07-27 11:05 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20120726T110441-843@post.gmane.org \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).