Disabling optimizations is definitely an option. I should check to see if disabling optimizations just for the one problem file makes the issue go away. No reason to disable optimizations for all files if necessary.
We have decided to only compile for 32bit and use that on all our 32 and 64 bit redhat systems. So from our perspective this issue is closed. -----Original Message----- From: Hyrum K Wright [mailto:hyrum.wri...@wandisco.com] Sent: Tuesday, August 16, 2011 10:56 AM To: Mark Phippard Cc: dev@subversion.apache.org; philip.mar...@wandisco.com; RYTTING,MICHAEL (A-ColSprings,ex1) Subject: Re: Problems compiling 1.7.0 on redhat el4 64bit On Tue, Aug 16, 2011 at 10:25 AM, Mark Phippard <markp...@gmail.com> wrote: > Where do we stand on this? I have not seen anyone propose the obvious > fix which would be to reverse the commit that caused the problem. Do > we really need this optimization if it can segfault with the wrong compiler > settings? > As mentioned before, we saw this same problem in the Linux RPM's that > we provide. Currently we are working around it by doing the build on > RHEL 5 and dropping support for RHEL 4, but obviously the preferred > solution for us would be to continue to support RHEL 4. I don't think we should revert this change, as it's a symptom of a compiler bug. If my understanding of this thread is correct, you could just disable optimizations for your RHEL 4 builds, and things should work, no? -Hyrum -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com/