subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Sperling <s...@stsp.name>
Subject Re: A subersion build environment on CentOS 7.2
Date Sun, 21 Aug 2016 11:00:06 GMT
On Sun, Aug 21, 2016 at 02:20:04AM -0500, horst.schlonz@gmx.de wrote:
> I successfully made a subversion build environment on CentOS 7.2 but I am
> not 100% satisfied because the Makefile.svn errored out two times so had to
> hack something. The commands I used are in subversion_buildenv.txt and the
> screenlog is in screenlog.0.gz.
> http://svn.apache.org/repos/asf/subversion/trunk/tools/dev/unix-build/Makefile.svn
> 
> First error is at line 8681 about gets being undeclared where I had to
> delete a certain line 1010 in a header file to make it go away.
> ./stdio.h:1010:1:error: gets undeclared here (not in a function)
> 
> The second error on line 14977 is about EC_GROUP_new_curve_GF2m being
> undeclared so I applied a patch that I found on Google.
> /root/svn/src/ruby-1.8.7-p374/ext/openssl/ossl_pkey_ec.c:815:29:Kerror:
> EC_GROUP_new_curve_GF2m undeclared (first use in this function)
> https://github.com/ruby/ruby/commit/0d58bb55985e787364b0235e5e69278d0f0ad4b0.patch
> 
> Maybe someone can shed light on the errors or suggest a better way to create
> an subversion build environment. I am not subscribed so please be so kind to
> add me to CC.
> 
> Regards

What are you trying to achive by building SVN with the Makefile from
tools/dev/unix-build/ ?

I wrote this Makefile for my own purposes because I need builds with
debugging symbols enabled in all dependencies. I use it on OpenBSD.
In the past, some SVN developers have used it on various Linux platforms.
At present I believe I'm the only active user.

This Makefile is not intended for setting up production installations of SVN.
It might serve as an example if you'd like to do a custom build of SVN and
its dependencies. But I won't provide support for purposes other than SVN
development.

If your goal is setting up a production environment, I would recommend
using binary packages system from http://subversion.apache.org/packages.html

If you don't use precompiled binaries you're essentially repeating the work
of a LInux distro package maintainer. If you insist on compiling your own
I'd recommend you compile against system libraries shipped with CentOS 7.2
as much as possible to avoid the kinds of problems you're seeing.
Building a Subversion release tarball, or even a trunk checkout, should be
possible with the proper RPM -devel packages installed for all dependencies.

Mime
View raw message