What I ended up doing was building everything across the NFS mount.
so rather than
local$ configure && make && make install
local$ cp to /path/to/remote/nfs/svn
local$ /path/to/remote/nfs/svn
i did
local$ /path/to/remote/nfs/svn/configure && make && make install
local$ /path/to/remote/nfs/svn
seems to work this way and not every client that can mount the nfs dir
can run the svn client without having it installed locally.
assuming that all systems are the same...
-Ryan
On Dec 9, 2003, at 3:05 PM, Kevin Pilch-Bisson wrote:
> Did you copy all of svn's shared libraries to the server too?
>
>> -----Original Message-----
>> From: Ryan Hunt [mailto:rhunt@hp.com]
>> Sent: Tuesday, December 09, 2003 1:22 PM
>> To: users@subversion.tigris.org
>> Subject: Bizarre version number change
>>
>> I just complied 0.34.0 as checked out from tags/0.34.0. When I run a
>> --version on it i get:
>>
>> => /home/rhunt/pub/source/build_svn/subversion/clients/cmdline/svn
>> --version
>> svn, version 0.34.0 (dev build)
>> compiled Dec 9 2003, 13:41:15
>>
>> however when I cp that to a file server so all the clients can mount
>> it
>> I get:
>>
>> => cp /home/rhunt/pub/source/build_svn/subversion/clients/cmdline/svn
>> .
>> => ./svn --version
>> svn, version 0.29.0 (r6976)
>> compiled Sep 26 2003, 17:33:58
>>
>> seems pretty strange anyone have and idea what might cause this and
>> how
>> to fix it?
>>
>> I used this method for 0.29.0 and now it seems like it is stuck in
>> that
>> mode.
>>
>> -Ryan
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: dev-help@subversion.tigris.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Dec 10 01:02:17 2003