bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Failure of IPv6 detection for BSD.


From: Mats Erik Andersson
Subject: Re: Failure of IPv6 detection for BSD.
Date: Sat, 18 Sep 2010 18:44:35 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

Dear Bruno,

lördag den 18 september 2010 klockan 17:19 skrev Bruno Haible detta:
> Mats Erik Andersson wrote:
> > The failing test is
> > 
> >     configure:31699: checking for struct sockaddr_in6
> 
> configure is generared from a multitude of files.
> 
> If you grep for 'for struct sockaddr_in6' in all *.m4, configure.ac, and 
> configure.in files in that project (or even everywhere on your system),
> where do you find the source code of that test?

The only hits are in "config.log" of different origins. Searches in most
parts of the file systems for Debian GNU/Linux and OpenBSD disclose this!

A further analysis points to this test

    ### inetutils/configure.ac, line 330
    ###

    if test ! "X$ipv6" = "Xno" && test "$working_ipv6" = "Xyes"; then
      AC_CHECK_TYPE(struct sockaddr_in6, , working_ipv6=no, [#include 
<netinet/in.h>])
    fi

When I take the expanded test in "configure" and I insert the missing
header file, like

    ### inetutils/configure, line 31698
    ###

    if test ....
        ac_fn_c_check_type "$LINENO" "struct sockaddr_in6" \
          "ac_cv_type_struct_sockaddr_in6" \
          "#include <sys/types.h>
    #include <netinet/in.h>
    "
    if test ...

    else
    fi
    fi

then I _do_ get the successful detection. As a result the __new__
config.log contains

    #define IPV6 1

which I was missing in the setup generated by bootstrap. With this
new knowledge I observe many tests in "configure.ac" that encapsulate
my manual insertion in a conditional on HAVE_SYS_TYPES_H. This is clearly
needed also in sensing "struct sockaddr_in6".

It seems to me that the blame must go to autoconf. Right? Or is the template
"configure.ac" maintained by GNU Inetutils incomplete?


Regards,
Mats



reply via email to

[Prev in Thread] Current Thread [Next in Thread]