From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: SIN_LEN and SIN_LEN6 in libguile/socket.c
Date: Wed, 25 Aug 2004 10:39:08 +1000 [thread overview]
Message-ID: <87oel0yrtf.fsf@zip.com.au> (raw)
In-Reply-To: <6F334972-F60A-11D8-A075-000D932C78D8@lurchi.franken.de> (Michael Tuexen's message of "Tue, 24 Aug 2004 22:16:08 +0200")
Michael Tuexen <Michael.Tuexen@lurchi.franken.de> writes:
>
> But there are not tests in
> the configure scripts to test for these fields and depending on that
> defining SIN_LEN or SIN_LEN6 or not.
That's a bug, but apparently not harmful on a gnu system (glibc
doesn't seem to have that field).
> AC_MSG_CHECKING(for sin_len)
> AC_TRY_COMPILE([#ifdef HAVE_SYS_TYPES_H
> ...
AC_CHECK_MEMBER?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-08-25 0:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 20:16 SIN_LEN and SIN_LEN6 in libguile/socket.c Michael Tuexen
2004-08-25 0:39 ` Kevin Ryde [this message]
2004-08-25 9:40 ` Michael Tuexen
2004-08-27 1:11 ` Kevin Ryde
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=87oel0yrtf.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).