Phil Pennock wrote:
> Hi,
>
> I've searched the list histories and the like and seen reports that IPv6
> is not supported but it must be a problem with external libraries. I'm
> not sure if this predates the current system, where the libraries are
> part of one build system ... I simply don't know enough about
> TortoiseSVN's history; I also don't have win32 dev tools so can't check
> this. Sorry. I don't develop on Win32, but do want to be able to
> support people who do, so have TortoiseSVN installed on a box to check
> it out.
>
> I too am getting problems with using IPv6-only hosts because TortoiseSVN
> reports that it couldn't resolve the hostname. Reading the trunk
> source, I see that neon is not being built with IPv6 support enabled; it
> needs to be turned on. I _think_ that it's just a matter of changing
> ext/build/neon.build to pass ENABLE_IPV6=yes.
>
> Justification follows.
>
> neon only uses the address resolution routines for modern address
> handling, including IPv6, if USE_GETADDRINFO is defined. This is
> ext/neon/src/ne_socket.c:ne_addr_resolve(). neon.mak contains:
> ----------------------------8< cut here >8------------------------------
> # Support for IPv6
> !IF "$(ENABLE_IPV6)" == "yes"
> IPV6_FLAGS = /D USE_GETADDRINFO
> !ENDIF
> ----------------------------8< cut here >8------------------------------
>
> ext/neon/INSTALL.win32 contains:
> ----------------------------8< cut here >8------------------------------
> Build neon with IPv6 support
> ____________________________
>
> To build neon with support for IPv6, use parameter ENABLE_IPV6.
>
> nmake /f neon.mak ENABLE_IPV6=yes
>
> This requires a copy of the Platform SDK which contains the IPv6
> headers and libraries.
> ----------------------------8< cut here >8------------------------------
>
> ext/build/neon.build appears to contain all the flags passed.
>
> QED.
Ahem: that QED is seriously flawed :)
* it's not just neon which needs IPv6 enabled. All other libraries which
handle networking also need it, especially apr.
* sure, we could enable IPv6. But then TSVN wouldn't work anymore on
win2k or XP without the separate dlls. And those dll's would have to be
installed by every user, downloaded from the MS website. The reason for
this is that apr doesn't check the existence of IPv6 support during
runtime but only on compile time. That means, once compiled with IPv6
support, apr *expects* the dll's to be present or it will not run at all.
So, if you really need IPv6 support, you must compile TSVN yourself. Sorry.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Sep 6 18:41:48 2006