Subject: Re: IPv6-enabled XFree86 4.4.0 with IPv4-only kernel
To: None <devel@xfree86.org, tech-x11@NetBSD.org>
From: David Dawes <dawes@XFree86.Org>
List: tech-x11
Date: 01/08/2004 17:44:45
On Thu, Jan 08, 2004 at 10:28:38PM +0100, Martin MOKREJS wrote:
>On Thu, 8 Jan 2004, David Dawes wrote:
>
>> On Thu, Jan 08, 2004 at 09:44:05PM +0100, Martin MOKREJS wrote:
>> >On Thu, 8 Jan 2004, David Dawes wrote:
>> >
>> >> On Thu, Jan 08, 2004 at 09:11:59PM +0100, Martin MOKREJS wrote:
>> >> >On Thu, 8 Jan 2004, David Dawes wrote:
>> >> >> >
>> >> >> >_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
>> >> >> >_XSERVTransOpen: transport open failed for inet6/krishna.mogua.com:0
>> >> >> >_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
>> >> >> >
>> >> >> >Fatal server error:
>> >> >> >Failed to establish all listening sockets
>> >> >>
>> >> >> You need to include -DPART_NET in your ServerOsDefines.  This makes
>> >> >> things like that non-fatal.  XFree86 servers build with this option
>> >> >> by default.
>> >> >
>> >> >I had the same problem on my Gentoo Linux box, I "fixed" that by enabling
>> >> >IPv6 in kernel. i just want to point out the flags should get into the
>> >> >mainstream distribution, or I'm desperate users who missed that critical
>> >> >requirement in RELNOTES .... :)
>> >>
>> >> Did you get a fatal error, or just a (harmless) warning message?
>> >> Like I said, for a default build of the XFree86 servers, this would
>> >> just be a non-fatal warning.
>> >
>> >That was fatal in my case.
>>
>> Do you know why?  I.e., did you modify anything in the build
>> configuration, or are you using some other source tree?
>
>No idea, haven't touched anything, just downloaded the release RC2 4.4.0
>candidate. I can try to reproduce in few days.

OK, it would be great to track this down.

David
-- 
David Dawes
developer/release engineer                      The XFree86 Project
www.XFree86.org/~dawes