On Mon, Aug 8, 2011 at 6:19 PM, <michael_rytting_at_agilent.com> wrote:
> For a while I was downloading and running the development build of
> subversion 1.7.0. At one revision of the code I started having an issue
> where svn would immediately segfault. At that time I stopped using 1.7.0
> assuming the issue would be fixed before release. Unfortunately I just
> downloaded the beta2 release of 1.7.0 and I’m having the same problem.
> Interestingly enough I can successfully build beta2 on one of our 32bit
> systems, but I can’t use that build on our 64 bit systems because it tries
> to link against the 32bit version of libmagic.
RHEL 4 is, frankly, way too old to support with new tools. It's
initial release was over six years, and far too many core libraries,
such as swig and sqlite and python, have not gotten updated to match
subversion requirements.
I'm trying to rebundle an SRPM for 1.6.17 for the RPMforge repository,
and no way am I burning the cycles to get it back to RHEL 4. The
1.7.0beta3 releases will compile well enough on RHEL 5, especially if
you build from an SRPM for 1.6.x first to get most of the dependencies
resolved.
RHEL 5, and Scientific Linux 5, have subversion-1.6.11 available from
the upstream vendor. Would that be enough for you?
Received on 2011-08-09 20:59:20 CEST