From: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org
Subject: Re: Thread + Socket + Pipes Bug?
Date: 15 Aug 2003 23:35:25 +0100 [thread overview]
Message-ID: <m37k5ey2fm.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <1060857843.545.4.camel@zuul>
>>>>> "Robert" == Robert Marlow <bobstopper@australispro.com.au> writes:
Robert> I've still got the guile-1.6.4 version I have installed available
Robert> though. I've put it in webspace at:
Robert> http://system.piscescom.com/~rmarlow/guile-1.6.4.tar.bz2
Robert> If you want to try that. I'll continue to see if I can get 1.7
Robert> installed. It'd be handy to have more version variance for my own
Robert> testing anyway.
Thanks, I've built and installed this now. I configured with
"./configure --with-threads" - does that match what you did?
Anyway, still no luck. I've added (format) statements all over so I
can see what's happening, and right now it seems that
./buggy-companion.scm isn't even starting up when invoked from the
worker threads of ./buggy.scm.
If, however, I just fire up Guile and do
guile> (use-modules (ice-9 popen))
guile> (use-modules (ice-9 threads))
guile> (define p (open-output-pipe "./buggy-companion.scm"))
guile> (display "hello there\n" p)
guile> (close-port p)
I see output indicating that ./buggy-companion.scm is running
correctly.
Any thoughts?
Neil
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2003-08-15 22:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 7:58 Thread + Socket + Pipes Bug? Robert Marlow
[not found] ` <m3adalb1ni.fsf@laruns.ossau.uklinux.net>
2003-08-08 1:09 ` Robert Marlow
2003-08-10 21:19 ` Neil Jerram
2003-08-11 10:02 ` bobstopper
2003-08-12 23:06 ` Neil Jerram
2003-08-14 10:43 ` Robert Marlow
2003-08-15 22:35 ` Neil Jerram [this message]
2003-08-14 14:08 ` Robert Marlow
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=m37k5ey2fm.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).