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

Re: newbie

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2002-02-28 22:52:54 CET

"Glenn A. Thompson" <gthompson@cdr.net> writes:

> I noticed that the INSTALL file recommends building static for clients
> and dynamic for server.

I think the INSTALL file recommends a static client for the initial
tarball build simply because this is the way the tarball gets
tested. The tarball build is just a way to provide a client to
checkout a current version of the Subversion code. The intention is
that a dynamic client will work. I use a dynamic client most of the
time.

> So I attempted to do what is suggested under "C. Building under Unix in
> Different Directories".
> I created a svrObj and a clntObj directory.
> I did the configure and a static build with ssl under clntObj. I didn't
> do a make install. I then used the new 'svn' binary to update and did
> another make. Cool. (I wanted to pick up the dup-string change)
> Next, I tried to build a dynamic version for installing a server.
> I did the configure and a dynamic build with ssl under svrObj. Cool.
> I try a make install. Buurrp. It can't find apr.exp. I found it under
> the source directory so I copy it under my svrObj.

It sounds like apr didn't get built when you built svrObj. Do you
object files under svrObj/apr (e.g. svrObj/apr/misc/unix/start.o)?

Did you build in the source directory at any stage? If you did then
this tends to disrupt the builddir != srcdir builds. If you did build
in the source dir, then it is best to run 'make clean' in the source
dir before attempting to build with builddir != srcdir.

-- 
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:10 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.