From: Andy Wingo <wingo@pobox.com>
To: Francis Southern <francis.southern@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: Stable 2.0 and popen.test on Debian Squeeze
Date: Sun, 27 Feb 2011 23:07:04 +0100 [thread overview]
Message-ID: <m3ei6trv1z.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTim=Dm6SqR2Fmd=oeP5oZT6AwbHD1_GPv0Hm6FZm@mail.gmail.com> (Francis Southern's message of "Thu, 24 Feb 2011 23:01:20 -0600")
On Fri 25 Feb 2011 06:01, Francis Southern <francis.southern@gmail.com> writes:
> As you may know, several people have been having problems with
> `popen.test' with 2.0 on Debian Squeeze. After a suggestion from
> Ludovic on IRC, I tried running it with my /bin/sh symlinked to Bash
> rather than Dash and there were no unexpected failures. Yay.
Whoa, that's a good one.
The difference seems to be the difference between:
dash -c 'exec 1>/dev/null; echo closed 1>&2; exec 2>/dev/null; read'
and
bash -c 'exec 1>/dev/null; echo closed 1>&2; exec 2>/dev/null; read'
Dash prints "closed" and exits immediately with error code 2. Bash
prints "closed" and waits for input from the "read".
Are we relying on non-portable shell behavior here?
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-02-27 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 5:01 Stable 2.0 and popen.test on Debian Squeeze Francis Southern
2011-02-27 22:07 ` Andy Wingo [this message]
2011-03-01 19:40 ` Mark H Weaver
2011-03-02 1:32 ` dsmich
2011-03-02 10:40 ` Mark H Weaver
2011-03-02 11:17 ` Mark H Weaver
2011-03-02 11:28 ` dsmich
-- strict thread matches above, loose matches on Subject: below --
2011-03-02 11:29 dsmich
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3ei6trv1z.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=francis.southern@gmail.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).