[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn co problems

From: Daniel Rall <dlr_at_collab.net>
Date: 2006-09-14 20:58:59 CEST

On Thu, 14 Sep 2006, Stefan Küng wrote:

> D.J. Heap wrote:
> >On 9/13/06, James Courtier-Dutton <James@superbug.co.uk> wrote:
> >[snip]
> >>This is all on windows, using the binaries downloaded from the svn site.
> >>I do not know what they are linked against.
> >>I have done some checking.
> >>svn 1.3.1 works.
> >>svn 1.4.0 fails
> >>
> >>TortoiseSVN 1.4.0 works.
> >>TortoiseSVN 1.3.1 fails.
> >>
> >>Maybe someone who built those versions can answer your question.
> >
> >
> >1.4.0 was built with a newer neon (0.26.1), but I don't know if SSPI
>
> I don't think that Subversion currently really works with neon 0.26.1.
> TSVN 1.4.0-dev is linked against neon 0.25.5, the same version as TSVN
> 1.3.5. The only difference is that 1.3.x has neon built with HAVE_SSPI
> set to "" instead of "1".

The INSTALL and neon.m4 for 1.4.0 does not support Neon 0.26.x.
Recently (r21490), a change did go into neon.m4 and
subversion/libsvn_ra_dav/session.c to support 0.26.x for the autoconf
build. Given the change to session.c, I'm somewhat surprised that
Subversion 1.4.0 compiled against 0.26.x.

  • application/pgp-signature attachment: stored
Received on Thu Sep 14 21:00:29 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.