unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Francis Southern <francis.southern@gmail.com>
To: bug-guile@gnu.org
Subject: Stable 2.0 and popen.test on Debian Squeeze
Date: Thu, 24 Feb 2011 23:01:20 -0600	[thread overview]
Message-ID: <AANLkTim=Dm6SqR2Fmd=oeP5oZT6AwbHD1_GPv0Hm6FZm@mail.gmail.com> (raw)

Hello Guilers,

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.

Upon further inspection, the problem is that the `open-output-pipe`
test, specifically the `(pass-if "no duplicate" ...' part, fails with
Dash but not Bash.
(I was checking this by running `./check-guile popen.test'.)

Incidentally, while trying to isolate the problem further, I
discovered that loading the file from the REPL gives me:
ERROR: open-output-pipe: no duplicate - arguments: ((wrong-type-arg
"string-append" "Wrong type (expecting ~A): ~S" ("string" #f) (#f)))

And all the other tests pass.  But I don't see how this error could be
related to the shell, and indeed it happens no matter what my system
shell is set to.

Unfortunately, I'm way out of my depth here and have no idea how to
proceed.  But if there's anything you think I can do to help I'm more
than willing to oblige.


I hope this helps!



             reply	other threads:[~2011-02-25  5:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25  5:01 Francis Southern [this message]
2011-02-27 22:07 ` Stable 2.0 and popen.test on Debian Squeeze Andy Wingo
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='AANLkTim=Dm6SqR2Fmd=oeP5oZT6AwbHD1_GPv0Hm6FZm@mail.gmail.com' \
    --to=francis.southern@gmail.com \
    --cc=bug-guile@gnu.org \
    /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).