From: Andy Wingo <wingo@pobox.com>
To: Marijn <hkBst@gentoo.org>
Cc: bug-guile@gnu.org
Subject: Re: guile-1.8.8 fails socket.test when linux is built without IPv6 (Address family not supported by protocol)
Date: Thu, 28 Apr 2011 22:31:11 +0200 [thread overview]
Message-ID: <m3y62uyv74.fsf@unquote.localdomain> (raw)
In-Reply-To: <4DA5AB4A.8060107@gentoo.org> (Marijn's message of "Wed, 13 Apr 2011 15:55:22 +0200")
On Wed 13 Apr 2011 15:55, Marijn <hkBst@gentoo.org> writes:
> another gentoo developer reports that Guile-1.8.8 fails socket.test when
> linux is built without CONFIG_IPV6=y:
>
> Running socket.test
> ERROR: In procedure socket:
> ERROR: Address family not supported by protocol
> FAIL: check-guile
In 2.0 this should not cause the test suite to exit prematurely, though
it may fail; dunno. I cherry-picked that fix back to 1.8.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-04-28 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 13:55 guile-1.8.8 fails socket.test when linux is built without IPv6 (Address family not supported by protocol) Marijn
2011-04-28 20:31 ` Andy Wingo [this message]
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=m3y62uyv74.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=hkBst@gentoo.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).