You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by thomas mauch <Th...@swisslog.com> on 2005/02/11 09:17:54 UTC

How to build the svn-client only from source tarball

Good morning
 
I need to build the command line svn client only on a HP-UX machine.
After running configure, I get a message saying that the build has been
configured for using the FSFS as back-end instead of the Berkeley DB - I
need no server however, just the command line client 'svn'. I looked at
the options of configure (configure --help) and read the INSTALL file,
but found nothing similar. Is there no way to build just the svn client
or am I missing something?
 
Thomas Mauch
 

____________________________________________________________
This message may contain legally privileged or confidential 
information and is therefore addressed to the named persons only. 
The recipient should inform the sender and delete this message, 
if he/she is not named as addressee. 
The sender disclaims any and all liability for the integrity 
and punctuality of this message. 
The sender has activated an automatic virus scanning by 
Messagelabs, but does not guarantee the virus free 
transmission of this message.

Re: How to build the svn-client only from source tarball

Posted by Steve Greenland <st...@lsli.com>.
On Fri, Feb 11, 2005 at 10:17:54AM +0100, thomas mauch wrote:
> I need to build the command line svn client only on a HP-UX machine.
> After running configure, I get a message saying that the build has been
> configured for using the FSFS as back-end instead of the Berkeley DB - I
> need no server however, just the command line client 'svn'. I looked at
> the options of configure (configure --help) and read the INSTALL file,
> but found nothing similar. Is there no way to build just the svn client
> or am I missing something?

There's no official way to build a "client-only" svn. But if you have a
working svn, don't worry about it. The lack of local BDB support doesn't
mean you can't use BDB on the real server.

Steve

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: How to build the svn-client only from source tarball

Posted by Max Bowsher <ma...@ukf.net>.
Chris Rose wrote:
> On Fri, 11 Feb 2005 15:38:24 -0600, Steve Greenland <st...@lsli.com> 
> wrote:
>> On Fri, Feb 11, 2005 at 09:09:47PM -0000, Max Bowsher wrote:
>>>
>>> I don't know whether autoconf supports options tweaking other options or
>>> not. But is "--without-apxs --without-berkeley-db" really too much for
>>> people to type? It's just 2 options!!!
>>
>> It's not the typing, it's figuring out which options to type. Also,
>> I was under the impression that I also needed "--without-apache
>> --without-swig --without-jdk -without-jikes --without-junit":  you
>> say those *should* be off by default, which is fine.
>
> Just a little extra .02 here:
>
> These disable options, do they affect the protocols supported by the
> client?  I'm trying to get a subversion client built on some
> non-standard Solaris 9 and Slackware systems, because the current svn
> client on the former only supports svn+ssh and the latter does not
> support DAV over SSL.
>
> I don't need the server binaries rebuilt, but I suspect that the
> reason the build is failing has something to do with that.  However,
> I'm leery of disabling so many options for fear of generating a client
> that doesn't do what I need it it.
>
> Any advice?

I think you should read the INSTALL file, and possibly start a new thread 
quoting exactly *how* your build is failing, and explaining exactly what you 
want to do.

The short version is:

ra_dav requires neon
ra_dav over SSL requires a neon which has been told to build against openssl

ra_svn requires no extras

ra_local with FSFS requires no extras
ra_local with BDB requires (obviously) BDB

Max.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: How to build the svn-client only from source tarball

Posted by Chris Rose <of...@gmail.com>.
On Fri, 11 Feb 2005 15:38:24 -0600, Steve Greenland <st...@lsli.com> wrote:
> On Fri, Feb 11, 2005 at 09:09:47PM -0000, Max Bowsher wrote:
> >
> > I don't know whether autoconf supports options tweaking other options or
> > not. But is "--without-apxs --without-berkeley-db" really too much for
> > people to type? It's just 2 options!!!
> 
> It's not the typing, it's figuring out which options to type. Also,
> I was under the impression that I also needed "--without-apache
> --without-swig --without-jdk -without-jikes --without-junit":  you
> say those *should* be off by default, which is fine.

Just a little extra .02 here:

These disable options, do they affect the protocols supported by the
client?  I'm trying to get a subversion client built on some
non-standard Solaris 9 and Slackware systems, because the current svn
client on the former only supports svn+ssh and the latter does not
support DAV over SSL.

I don't need the server binaries rebuilt, but I suspect that the
reason the build is failing has something to do with that.  However,
I'm leery of disabling so many options for fear of generating a client
that doesn't do what I need it it.

Any advice?

(Yes, I know that this is a bit of a derail)

-- 
Chris R.
======
Not to be taken literally, internally, or seriously.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: How to build the svn-client only from source tarball

Posted by Steve Greenland <st...@lsli.com>.
On Fri, Feb 11, 2005 at 09:09:47PM -0000, Max Bowsher wrote:
> 
> I don't know whether autoconf supports options tweaking other options or 
> not. But is "--without-apxs --without-berkeley-db" really too much for 
> people to type? It's just 2 options!!!

It's not the typing, it's figuring out which options to type. Also,
I was under the impression that I also needed "--without-apache
--without-swig --without-jdk -without-jikes --without-junit":  you
say those *should* be off by default, which is fine.

As I said, I think the balls in my court now to write a patch whose
value outweighs its complexity, and submit it to -dev. Until I've done
that, I promise to not comment anymore on this topic. :-)

Steve

-- 
"Outlook not so good." That magic 8-ball knows everything! I'll ask
about Exchange Server next.
                           -- (Stolen from the net)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: How to build the svn-client only from source tarball

Posted by Max Bowsher <ma...@ukf.net>.
Steve Greenland wrote:
> On Fri, Feb 11, 2005 at 08:02:07PM -0000, Max Bowsher wrote:
>> Steve Greenland wrote:
>> Client only-ness only applies to the compilation of svnserve. That's 
>> _one_
>> C file, and _one_ program link. A tiny amount of processing compared to 
>> the
>> rest of the compilation.
>>
>>> In particular, I could significant time on some of my machines if I
>>> could tell it
>>> I think they are not always passed to the sub-configures.)
>>
>> Subconfigures? The only subconfigures run are apr, apr-util, and neon.
>
> I thought I had previously posted the relevant parts of the configure
> logs; I'll need to dig them out again, I guess.
>
>>
>> Are you speaking of apr-util still looking for BDB? That's the only thing 
>> I
>> can think of.
>>
>> If so, see the apr-util configure --help for appropriate flags.
>
> Ummm, if I pass --without-berkeley-db to subversion's configure, it
> needs to pass the appropriate flags to apr-util. (And it might well be: I
> don't remember the exact problem I was seeing.)

On looking into this more closely, it appears that apr-util 
understands --without-berkeley-db, and the standard passing of arguments to 
subconfigures should take care of this.

So, if you can find out if and why this is not happening, we want to know 
about it.

>>> language bindings, etc.
>> Aren't built by default anyway.
>
> Then why are the configures looking for SWIG and Python? That I *do* 
> remember.

At the moment, configure looks regardless. Not wonderful. One of the things 
I want to try and fix, some time. Patches welcome.

>>> For those of us who need to support a variety of
>>> architectures locally, this would be useful.
>>
>> If you are supporting a variety of architectures, surely it can't be too
>> much trouble to write a 1-line script containing your preferred 
>> ./configure
>> invocation?
>
> Nope, but that only help me.

Most cases configure should just do the right thing without special options 
anyway.

>> A few emails here and there, versus a non-trivial amount of extra
>> complexity in the build-system.
>
> Is making --client-config an alias for a combination of various
> --without* and --disable* options really a big deal? (Forget not
> building svnadmin et. al., you're right, it's not that big a deal.)

I don't know whether autoconf supports options tweaking other options or 
not. But is "--without-apxs --without-berkeley-db" really too much for 
people to type? It's just 2 options!!!

Max.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: How to build the svn-client only from source tarball

Posted by Steve Greenland <st...@lsli.com>.
On Fri, Feb 11, 2005 at 08:02:07PM -0000, Max Bowsher wrote:
> Steve Greenland wrote:
> Client only-ness only applies to the compilation of svnserve. That's _one_ 
> C file, and _one_ program link. A tiny amount of processing compared to the 
> rest of the compilation.
> 
> >In particular, I could significant time on some of my machines if I
> >could tell it
> >I think they are not always passed to the sub-configures.)
> 
> Subconfigures? The only subconfigures run are apr, apr-util, and neon.

I thought I had previously posted the relevant parts of the configure
logs; I'll need to dig them out again, I guess.

> 
> Are you speaking of apr-util still looking for BDB? That's the only thing I 
> can think of.
> 
> If so, see the apr-util configure --help for appropriate flags.

Ummm, if I pass --without-berkeley-db to subversion's configure, it
needs to pass the appropriate flags to apr-util. (And it might well be: I don't
remember the exact problem I was seeing.)

> >language bindings, etc.
> Aren't built by default anyway.

Then why are the configures looking for SWIG and Python? That I *do* remember.

> >For those of us who need to support a variety of
> >architectures locally, this would be useful.
> 
> If you are supporting a variety of architectures, surely it can't be too 
> much trouble to write a 1-line script containing your preferred ./configure 
> invocation?

Nope, but that only help me.

> A few emails here and there, versus a non-trivial amount of extra 
> complexity in the build-system.

Is making --client-config an alias for a combination of various
--without* and --disable* options really a big deal? (Forget not
building svnadmin et. al., you're right, it's not that big a deal.)

> So, I'm voting -0 on a --client-only patch.
> That's not a veto - you can try mail dev@ and persuade some other 
> committers that it would be good idea if you like - but I personally won't 
> be the one approving this.

Well, time for me to put up or shut up. :-) I God, I hate messing with
autoconf...

Steve

-- 
"Outlook not so good." That magic 8-ball knows everything! I'll ask
about Exchange Server next.
                           -- (Stolen from the net)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: How to build the svn-client only from source tarball

Posted by Max Bowsher <ma...@ukf.net>.
Steve Greenland wrote:
> On Fri, Feb 11, 2005 at 02:59:31PM -0000, Max Bowsher wrote:
>>
>> There is no way to select a client only build, because the only thing you
>> would save would be 5-10 seconds of compilation time, which is rather
>> irrelevant in the context of the several minutes for the rest of the 
>> build.
>
> It must be a pleasure to never have to work on slow machines.

Client only-ness only applies to the compilation of svnserve. That's _one_ C 
file, and _one_ program link. A tiny amount of processing compared to the 
rest of the compilation.

> In particular, I could significant time on some of my machines if I
> could tell it
>
> - Don't even look for BDB
> - Don't even look for Apache stuff
> - Don't even look for SWIG, or python, or perl, or java.
>
> (Yes, there are options to do that, and I use them.

Excellent, that's what they are there for.

> But they don't work reliably

If so, we would be happy to listen to bug reports and fix it.

> I think they are not always passed to the sub-configures.)

Subconfigures? The only subconfigures run are apr, apr-util, and neon.

Are you speaking of apr-util still looking for BDB? That's the only thing I 
can think of.

If so, see the apr-util configure --help for appropriate flags.

> Max, I understand you don't care about this. Would you accept a patch
> that implemented a reasonable --client-only, for those of us that do?
> I think a reasonable 'client-only' definition is

> no BDB support, and

Which will happen on it's own if BDB is not found. (Via a *quick* test 
querying apr-util).

> built only svn, no attempt to build the admin tools,

svnserve and svnlook could be left out, but the compilation time of those 
compared to the libraries makes the extra configure machinery to 
conditionalize them seem vastly overcomplicated.

> webdav stuff,

Won't be built anyway if apxs isn't found.

> language bindings, etc.

Aren't built by default anyway.

> For those of us who need to support a variety of
> architectures locally, this would be useful.

If you are supporting a variety of architectures, surely it can't be too 
much trouble to write a 1-line script containing your preferred ./configure 
invocation?

> If nothing else, it would
> shutup the people who can't find the --client-only configuration option.

A few emails here and there, versus a non-trivial amount of extra complexity 
in the build-system.

So, I'm voting -0 on a --client-only patch.
That's not a veto - you can try mail dev@ and persuade some other committers 
that it would be good idea if you like - but I personally won't be the one 
approving this.

Max.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: How to build the svn-client only from source tarball

Posted by Steve Greenland <st...@lsli.com>.
On Fri, Feb 11, 2005 at 02:59:31PM -0000, Max Bowsher wrote:
> 
> There is no way to select a client only build, because the only thing you 
> would save would be 5-10 seconds of compilation time, which is rather 
> irrelevant in the context of the several minutes for the rest of the build.

It must be a pleasure to never have to work on slow machines.

In particular, I could significant time on some of my machines if I
could tell it

- Don't even look for BDB
- Don't even look for Apache stuff
- Don't even look for SWIG, or python, or perl, or java.

(Yes, there are options to do that, and I use them. But they don't work
reliably - I think they are not always passed to the sub-configures.)

Max, I understand you don't care about this. Would you accept a patch
that implemented a reasonable --client-only, for those of us that do?
I think a reasonable 'client-only' definition is no BDB support, and
built only svn, no attempt to build the admin tools, webdav stuff,
language bindings, etc. For those of us who need to support a variety of
architectures locally, this would be useful. If nothing else, it would
shutup the people who can't find the --client-only configuration option.

Steve

-- 
"Outlook not so good." That magic 8-ball knows everything! I'll ask
about Exchange Server next.
                           -- (Stolen from the net)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: How to build the svn-client only from source tarball

Posted by Max Bowsher <ma...@ukf.net>.
thomas mauch wrote:
> Good morning
>
> I need to build the command line svn client only on a HP-UX machine.
> After running configure, I get a message saying that the build has been
> configured for using the FSFS as back-end instead of the Berkeley DB - I
> need no server however, just the command line client 'svn'. I looked at
> the options of configure (configure --help) and read the INSTALL file,
> but found nothing similar. Is there no way to build just the svn client
> or am I missing something?

There is no way to select a client only build, because the only thing you 
would save would be 5-10 seconds of compilation time, which is rather 
irrelevant in the context of the several minutes for the rest of the build.

Max.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org