On Tue, Aug 9, 2011 at 2:58 PM, Nico Kadel-Garcia <nka...@gmail.com> wrote:
> On Mon, Aug 8, 2011 at 6:19 PM, <michael_rytt...@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. > Whether it is a good idea and whether it ought to work are really two separate conversations. 1.7 was building fine on RHEL 4 and then stopped working. Is that a bug that should be fixed? I think so. It might be up to Michael to track down what caused the breakage though. Like I said, I also saw this problem but I was able to move to RHEL 5. So I lacked motivation to solve it on RHEL 4. In my case, I build my own version of all of the dependencies, the versions that come from Red Hat does not matter to me. Exception being gcc and libc etc. -- Thanks Mark Phippard http://markphip.blogspot.com/
