Thanks for the input. As for the ELF interpreter, I'm not sure what the
problem is. When I build everything shared, the ELF interpreter is fine
because the Subversion executables are linked with libc.so.6 , which is
available. When I change things to more of a static build, libc.so.1 is
used and is not present on the system. I've started with fresh builds
everytime it has filed. I even remove all sources and reextract the
tarballs. I am at a loss. I may have found something but I don't want to
discuss until I prove/disprove it.
On 4/14/07, David James <firstname.lastname@example.org> wrote:
> On 4/13/07, Jeremy Whitlock <email@example.com> wrote:
> > 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:
> Hi Jeremy,
> If you're trying to build Subversion statically, a good place to start
> is with D.J. Hagberg's static build. If you look inside the
> svn-linux-build.zip file you'll see that D.J. has scripts which
> carefully configure all of the dependencies.
> I recommend starting with his script and adding any additional
> dependencies to that.
> If you got a bad ELF interpreter error, it likely means that one of
> the files in your build got corrupted somehow, or that you built some
> of the binaries on a different processor architecture. That's my
> experience anyway. To avoid this error, it would be a good idea to
> start fresh with a clean build.
Received on Sat Apr 14 17:56:02 2007