Re: ipv6 default in current ports?

2000-02-20 Thread sumikawa
Chris> It doesn't need kernel support to build with ipv6 support. Chris> Trying to use the ipv6 support without it in the kernel is the Chris> only problem. dgilbert> Well... ruby refuses to build with IPv6 if it's not enabled and mtr dgilbert> dies with a "cannot open socket". dgilbert> In esce

Re: ipv6 default in current ports?

2000-02-18 Thread David Gilbert
> "Chris" == Chris Piazza <[EMAIL PROTECTED]> writes: Chris> On Fri, Feb 18, 2000 at 05:26:45PM -0500, David Gilbert wrote: >> I've come up against a number of ports lately assume IPv6 support >> if you're running: >> >> .if ${OSVERSION} >= 400014 CONFIGURE_ARGS+= --enable-ipv6 .endif >> >>

Re: ipv6 default in current ports?

2000-02-18 Thread Chris Piazza
On Fri, Feb 18, 2000 at 05:26:45PM -0500, David Gilbert wrote: > I've come up against a number of ports lately assume IPv6 support if > you're running: > > .if ${OSVERSION} >= 400014 > CONFIGURE_ARGS+= --enable-ipv6 > .endif > > ... I don't see INET6 in my GENERIC kernel. This affects at least

ipv6 default in current ports?

2000-02-18 Thread David Gilbert
I've come up against a number of ports lately assume IPv6 support if you're running: .if ${OSVERSION} >= 400014 CONFIGURE_ARGS+= --enable-ipv6 .endif ... I don't see INET6 in my GENERIC kernel. This affects at least net/mtr and lang/ruby. Dave. --