From: Noah Lavine <noah.b.lavine@gmail.com>
To: guile-devel@gnu.org
Subject: Bug in Guile's Posix Networking
Date: Mon, 7 Feb 2011 01:28:07 -0500 [thread overview]
Message-ID: <AANLkTim_QmEWaBd8=1zdvT5-RBvivJ=wYsFB1Uv_qmpj@mail.gmail.com> (raw)
Hello all,
I think there's a bug in Guile's Posix networking capabilities. I
first noticed it a few days ago when I couldn't get the example web
server to work on my system (Mac OS X 10.6). I was getting an error
from the bind command saying "can't assign requested address". I
assumed it was a system configuration problem until I discovered that
an equivalent Python program could bind a socket without trouble.
The full story is at
http://serverfault.com/questions/231941/why-cant-i-bind-to-127-0-0-1-on-mac-os-x
(I know the Python program listed is not quite identical to the Scheme
one, but I tried it with an actually identical Scheme program and
still got the same error.) Interestingly enough, I was able to bind a
socket in Guile if I specified INADDR_ANY as its address instead of
127.0.0.1.
I hope to work on this soon, but I thought I'd ask on this list if
anyone has an idea what might be causing this.
Thanks,
Noah
next reply other threads:[~2011-02-07 6:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 6:28 Noah Lavine [this message]
2011-02-07 23:49 ` Bug in Guile's Posix Networking Andreas Rottmann
2011-02-12 20:47 ` Noah Lavine
2011-02-12 21:02 ` Andy Wingo
2011-02-12 21:35 ` Noah Lavine
2011-02-12 22:00 ` Andy Wingo
2011-02-13 1:22 ` Noah Lavine
2011-02-13 1:45 ` Noah Lavine
2011-02-13 2:22 ` Noah Lavine
2011-02-13 3:00 ` Noah Lavine
2011-02-13 5:42 ` Ken Raeburn
2011-02-13 13:55 ` Noah Lavine
2011-02-13 13:57 ` Noah Lavine
2011-02-13 18:34 ` Ken Raeburn
2011-02-13 20:07 ` Andy Wingo
2011-02-13 20:10 ` Noah Lavine
2011-02-13 20:34 ` Noah Lavine
2011-02-13 21:10 ` Andy Wingo
2011-02-13 20:04 ` Andy Wingo
2011-02-12 11:26 ` Andy Wingo
2011-02-12 20:33 ` Noah Lavine
2011-02-12 20:59 ` Andy Wingo
2011-02-12 21:00 ` Noah Lavine
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_QmEWaBd8=1zdvT5-RBvivJ=wYsFB1Uv_qmpj@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@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).