...and even worse it gets. See below.
Ben Collins-Sussman wrote:
> On Mon, 2003-12-29 at 15:28, Garret Wilson wrote:
>
>>This gets even worse:
>>
>>I downloaded a brand new 0.35.1 tarball, and ran make (but not make
>>install). There were no errors. subversion/clients/cmdline/svn then gives:
>>
>>Segmentation fault (core dumped)
>
> It sounds like you either have libc problems, or that (somehow) your svn
> binary linked against older libsvn_* libraries in your system. Is that
> possible? Look at 'ldd' output. Purge your system of old libraries.
I removed all the svn libraries, and then made a client-only svn from
the 0.32.1 tarball. Same core dump. Now I *know* something is horribly
wrong, because 0.32.1 is the version I was running nicely before this
whole ordeal started.
With a client-only 0.32.1, the new Berkeley DB shouldn't be an issue. As
this is straight from the tarball, the new neon shouldn't be an issue,
either. That leaves only two things that I've changed: Python and gcc.
The latest subversion wouldn't build with the pre-2.0 Python I had been
using on all the other revisions, so I had to upgrade. Problem is, Red
Hat 7.0 has a gcc bug that won't let Python 2.0 build, so I had to
upgrade gcc.
I originally had some old glibc RPM that came with Red Hat 7.0---maybe
2.1.9x. At some point before today, I had downloaded, built, and
installed glibc 2.3.2 from source. This apparently didn't change the gcc
header file needed by Python to correctly compile (see LONG_BIT
definition issue at
http://www.python.org/cgi-bin/moinmoin/Python20FrequentlyAskedQuestions ).
I therefore upgraded Red Hat glibc by using:
rpm -Uvh glibc-2.2.4-18.7.0.9.i686.rpm
glibc-common-2.2.4-18.7.0.9.i386.rpm glibc-devel-2.2.4-18.7.0.9.i386.rpm
This upgrade seemed to go fine. I don't know what this did to the
glibc-2.3.2 I had installed from the source, however.
Everything builds fine, with no errors. I still get core dumps. Any,
*any* help will be extremely appreciated.
Garret
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 29 23:49:50 2003