unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: SIN_LEN and SIN_LEN6 in libguile/socket.c
Date: Tue, 24 Aug 2004 22:16:08 +0200	[thread overview]
Message-ID: <6F334972-F60A-11D8-A075-000D932C78D8@lurchi.franken.de> (raw)

Dear all,

the sin_len and sin_len6 field is not available on all platforms. 
Therefore
the code setting these fields is #ifdefed. 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.

I think something like

AC_MSG_CHECKING(for sin_len)
AC_TRY_COMPILE([#ifdef HAVE_SYS_TYPES_H
                 #include <sys/types.h>
                 #endif
                 #include <netinet/in.h>],
                [struct sockaddr_in x; x.sin_len = 0;],
                [AC_DEFINE(HAVE_SIN_LEN, 1 [Define this if your IPv4 has 
sin_len in sockaddr_in struct.])
                 AC_MSG_RESULT(yes)],
                [AC_MSG_RESULT(no)])

AC_MSG_CHECKING(for sin6_len)
AC_TRY_COMPILE([#ifdef HAVE_SYS_TYPES_H
                 #include <sys/types.h>
                 #endif
                 #include <netinet/in.h>],
                [struct sockaddr_in6 x; x.sin6_len = 0;],
                [AC_DEFINE(HAVE_SIN6_LEN, 1, [Define this if your IPv6 
has sin6_len in sockaddr_in6 struct.])
                 AC_MSG_RESULT(yes)],
                [AC_MSG_RESULT(no)])

should be added to configure.in and SIN_LEN/SIN_LEN6 should be changed 
to HAVE_SIN_LEN/HAVE_SIN6_LEN
to be consistent with other names.

Best regards
Michael



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


             reply	other threads:[~2004-08-24 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 20:16 Michael Tuexen [this message]
2004-08-25  0:39 ` SIN_LEN and SIN_LEN6 in libguile/socket.c Kevin Ryde
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=6F334972-F60A-11D8-A075-000D932C78D8@lurchi.franken.de \
    --to=michael.tuexen@lurchi.franken.de \
    /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).