[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Compiling Static Subversion Binaries on RHEL

From: Jeremy Whitlock <jcscoobyrs_at_gmail.com>
Date: 2007-04-14 08:15:31 CEST

Hi All,
    I have spent over 12 hours today trying to build a static Subversion
binary, and static binary dependencies of Subversion, on RHEL. After
fighting with apr-util and OpenLDAP, I finally decided to stop building
OpenLDAP statically and got Apache compiled and running. The problem is
when I build Subversion statically on RHEL, I get the following error:

bad ELF interpreter: No such file or directory

The above occurs when running any of the Subversion executables and it
appears that libc.so.1 is what is not being found. What mystifies me is
that libc.so.6 is installed on the system and in the desired location. I am
not sure what is going on but I am out of ideas. configure commands for
Subversion and all dependencies will be made available as necessary. Can
someone please shed some light on this? Google and irc have turned up
fruitless to this point. Before I go, let me give just a little more
detail.

I have attempted to compile all of Subversion's dependencies statically.
This is not a problem until you want apr-util to work with a statically
compiled OpenLDAP. After not finding a solution for that problem, I then
recompiled OpenLDAP with shared libraries and apr-util compiled properly.
When I get to the point of compiling Subversion, I am attempting to build a
completely static/standalone installation. The compilation goes fine but
when the installation part kicks off, you see a lot of the errors above when
the installation process tries to run the newly compiled executables. I
then try to execute one of the compiled binaries and I get the above error.
ldd also fails with this error when ran against the Subversion executables.

Take care,

Jeremy
Received on Sat Apr 14 08:15:51 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.