Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 29 Oct 2016 20:05:22 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 213898] net/mDNSResponder unconditionally enables IPV6
Message-ID:  <bug-213898-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213898

            Bug ID: 213898
           Summary: net/mDNSResponder unconditionally enables IPV6
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: sunpoet@FreeBSD.org
          Reporter: mi@FreeBSD.org
             Flags: maintainer-feedback?(sunpoet@FreeBSD.org)
          Assignee: sunpoet@FreeBSD.org

Created attachment 176292
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D176292&action=
=3Dedit
Turn off HAVE_IPV6, if WITHOUT contains "IPV6"

The port goes through some effort to enable IPV6 functionality. Unfortunate=
ly,
it does so unconditionally -- even where the OS and the kernel are built
without it. On such systems the resulting daemons refuse to even start:

% /usr/local/bin/mDNSResponderPosix ....
socket AF_INET6: Address family not supported by protocol family

The enclosed patch examines the local machine's WITHOUT-setting and turns o=
ff
the HAVE_IPV6 flag, if IPV6 is disabled.

Rebuilt thus, the daemon can start on my machines here.

The proper fix would've been for the upstream to stop treating the run-time
absence of AF_INET6-support as fatal. But that may be too much for the port=
 to
fix...

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-213898-13>