Re: SIGSEGV with 1.7.8 on Centos 4.8

2013-02-12 Thread Benson Margulies
That did it. Thanks. On Tue, Feb 12, 2013 at 1:50 PM, Philip Martin wrote: > Benson Margulies writes: > >> I built from the source, after running get-deps.sh, on Centos 4.8. All >> commands, including svn help, SIGSEGV. Here's the backtrace. >> >> I used no options to configure except prefix. >>

Re: SIGSEGV with 1.7.8 on Centos 4.8

2013-02-12 Thread Benson Margulies
Should adding -disable-nonportable-atomics to the configure command at top level do the job? On Tue, Feb 12, 2013 at 1:50 PM, Philip Martin wrote: > Benson Margulies writes: > >> I built from the source, after running get-deps.sh, on Centos 4.8. All >> commands, including svn help, SIGSEGV. Her

Re: SIGSEGV with 1.7.8 on Centos 4.8

2013-02-12 Thread Philip Martin
Benson Margulies writes: > I built from the source, after running get-deps.sh, on Centos 4.8. All > commands, including svn help, SIGSEGV. Here's the backtrace. > > I used no options to configure except prefix. > > Any suggestions for this? > > #0 0x in ?? () > #1 0x00399681

Re: SIGSEGV with 1.7.8 on Centos 4.8

2013-02-12 Thread Nico Kadel-Garcia
On Tue, Feb 12, 2013 at 11:49 AM, Benson Margulies wrote: > I built from the source, after running get-deps.sh, on Centos 4.8. All > commands, including svn help, SIGSEGV. Here's the backtrace. > > I used no options to configure except prefix. get-deps.sh is often uselessly out of date, because t

SIGSEGV with 1.7.8 on Centos 4.8

2013-02-12 Thread Benson Margulies
I built from the source, after running get-deps.sh, on Centos 4.8. All commands, including svn help, SIGSEGV. Here's the backtrace. I used no options to configure except prefix. Any suggestions for this? #0 0x in ?? () #1 0x00399681d578 in __gconv () from /lib64/tls/libc.so