RE: Problems compiling 1.7.0 on redhat el4 64bit

I tried running -O2 and -O1, both were crashing as well. Only completely disabling optimizations will cause the segfault to stop.

-----Original Message-----
From: David Chapman [mailto:dcchapman_at_acm.org]
Sent: Wednesday, August 10, 2011 5:39 PM
To: RYTTING,MICHAEL (A-ColSprings,ex1)
Cc: philip.martin_at_wandisco.com; markphip_at_gmail.com; dev_at_subversion.apache.org; users_at_subversion.apache.org
Subject: Re: Problems compiling 1.7.0 on redhat el4 64bit

On 8/10/2011 4:12 PM, michael_rytting_at_agilent.com wrote:
> It is set to 1
>
> On Aug 10, 2011, at 3:51 PM, "Philip Martin"<philip.martin_at_wandisco.com> wrote:
>
>> <michael_rytting_at_agilent.com> writes:
>>
>>> If I disable optimizations by doing "make CFLAGS=-O0" the program no
>>> longer crashes.
>> That suggests it could be a compiler bug.

Sorry to jump in so late, but I had significant problems with optimization for 64-bit executables under CentOS 4.x. If you can't upgrade, I suggest dialing down the optimization flags. I had to drop from -O3 to -O2 so that Crypto++ 5.5.2 would run, for example. At some point I could drop support for RHEL/CentOS 4.x from my client's products and try going back to -O3, but the required testing hasn't been real high on the priority list.

Assuming the SVN configuration scripts can distinguish between the releases, I suspect that changing the default optimization flags for RHEL 4.x will be simpler than trying to fix the new UTF-8 code. Have you tried intermediate levels of optimization? We went to production with -O2, so it's not as if all 64-bit optimizations were broken.

-- 
     David Chapman         dcchapman_at_acm.org
     Chapman Consulting -- San Jose, CA