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

Re: Strange Problem with SVN Command-Line client (self-compiled)

From: Ryan Schmidt <subversion-2008b_at_ryandesign.com>
Date: Thu, 26 Jun 2008 15:30:57 -0500

On Jun 26, 2008, at 03:15, Lars Tiefland wrote:

> 2008/6/25, Ryan Schmidt:
>
>> On Jun 25, 2008, at 05:41, Lars Tiefland wrote:
>>
>>> I've compilded SVN 1.5.0 on Debian Etch by Hand with the following
>>> ./configure command line:
>>>
>>> ./configure --prefix=/usr --disable-mod-activation
>>>
>>> Afterwards I've restarted Apache 2.2.3 to let the server load the
>>> new
>>> libraries. Everythig is working fine so far, if I use a different
>>> client.
>>>
>>> When using the commandline client provided by SVN I get the
>>> following message:
>>>
>>> svn: Unrecognized URL scheme for 'http://server2/svn/content-
>>> management/trunk'
>>>
>>> What's up there?
>>
>>
>> Neither the neon nor serf libraries were found when you compiled
>> your svn
>> client, therefore it can't communicate with http or https
>> repositories.
>> Install neon or serf, then recompile svn and tell it (during the
>> configure
>> phase) where neon or serf are located.
>
> @Ryan: Thanks! That worked. I thought, that the compile process would
> use the system libraries, if I don't install the dependency tarball.
> On the other hand I've just noticed that the neon dev-files had not
> been installed on the system.Now that I've unpacked the
> subversion-dep-1.5.0 tarball everything works fine. Perhaps the
> configure script should fail, if the webdav library gets compiled and
> neither neon nor serf dev-files were found on the system.

I don't think anything needs to be changed. How is Subversion to know
that you intend to use your binaries as both a server and a client
unless you tell Subversion this? You could just as easily be
intending to make just a server, on which serf and neon wouldn't be
needed. Or you could be intending to make just a client, on which
apache wouldn't be needed.

Now I haven't tested this, but hopefully if you specify --with-serf=/
foo or --with-neon=/foo and it doesn't find those libraries in /foo
then it would exit with an error.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-26 22:31:23 CEST

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

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