SVN repository on bluehost

[Plec]

I could successfully compile and install apt and apt-util.
Unfortunately libtool breaks during the subversion build with:
...
/usr/lib/libexpat.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status

I was wondering if that could have anything to do with the 64bit version of my host:
$ uname -a
Linux box307.bluehost.com 2.6.21-3_1.BHsmp #1 SMP Fri Jun 1 09:45:19 MDT 2007 x86_64 x86_64 x86_64 GNU/Linux

Has anybody similar experiences?
Thanks!

I added -L/lib64 to the gcc command to solve this issue

/bin/sh /home/username/build/libtool --silent --mode=link gcc -g -O2 -pthread -DHAVE_CONFIG_H -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -L/lib64 [.....] -lpthread -ldl

Normaly, export LDFLAGS="-L/lib64" should work, but it was not working for apr-util. But you will need it to compile subversion or you will see the same error /usr/lib/libexpat.so: could not read symbols: File in wrong format

[luissquall]

I added -L/lib64 to the gcc command to solve this issue

/bin/sh /home/username/build/libtool --silent --mode=link gcc -g -O2 -pthread -DHAVE_CONFIG_H -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -L/lib64 [.....] -lpthread -ldl

Normaly, export LDFLAGS="-L/lib64" should work, but it was not working for apr-util. But you will need it to compile subversion or you will see the same error /usr/lib/libexpat.so: could not read symbols: File in wrong format

I'm still having a problem: libtool: link: you must specify an output file
What output file should I have to create? Where do I have to locate it? what does [...] means?

Thanks!

[gursesl]

Seems you're trying to modify a system lib folder.

Add these lines into ~/.bash_profile
* export PYTHONPATH="$HOME/lib/python2.3/site-packages"
* export LD_LIBRARY_PATH="$HOME/lib"

Then run the command with to add --prefix=$HOME.

[Plec]

luissquall,

The [...] means that I stripped the command (too much characters). You need to cut and paste all of your libtool command (from which the compile error came from). The line starts with /bin/sh /home/your_username/build/libtool --silent ... and finish by some librairies like -lpthread -ldl). After that, don't forget to add -L/lib64 to your paste (see previous post). After continue with make and make install.

[davemac]

When I follow the instructions above and paste my /bin/bash command with the added '-L/lib64' I get the following error:

libtool: link: 'commit.lo' is not a valid libtool object

I would appreciate any help, as I really would like SVN up and running.

[doubled_man]

davemac,

Where are you in your installation? Have you installed the apr, apr-util, neon and subversion files?

[birdsnare]

I am having the same problem. I have neon, apr, and apr-util installed. I configured subversion 1.4.3 as follows:

./configure --prefix=$HOME --without-berkeley-db --with-zlib --with-ssl


When I run make, this is where it breaks, and this is the error I get.

cd subversion/libsvn_subr && /bin/sh /home/mydomain/source/subversion-1.4.3/libtool --tag=CC --silent --mode=link gcc -g -O2 -g -O2 -pthread -rpath /home/mydomain/lib -o libsvn_subr-1.la auth.lo cmdline.lo compat.lo config.lo config_auth.lo config_file.lo config_win.lo constructors.lo ctype.lo date.lo dso.lo error.lo hash.lo io.lo kitchensink.lo lock.lo md5.lo nls.lo opt.lo path.lo pool.lo prompt.lo quoprint.lo simple_providers.lo sorts.lo ssl_client_cert_providers.lo ssl_client_cert_pw_providers.lo ssl_server_trust_providers.lo stream.lo subst.lo svn_base64.lo svn_string.lo target.lo time.lo user.lo username_providers.lo utf.lo utf_validate.lo validate.lo version.lo xml.lo /home/mydomain/lib/libaprutil-1.la -lpq -lexpat /home/mydomain/lib/libapr-1.la -luuid -lrt -lcrypt -lpthread -ldl -lz
/usr/lib/libexpat.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
make: *** [subversion/libsvn_subr/libsvn_subr-1.la] Error 1

I'm not really sure where I need to put the L/lib64 in this. I did it with apr and apr-util with no problem, but everything I try with this fails in the same was described in the post above. I always get something to the effect of

libtool: link: `dag.lo' is not a valid libtool object

[birdsnare]

When configuring Subversion, I entered

./configure --prefix=$HOME --without-berkeley-db --with-zlib --with-ssl LDFLAGS="-L/lib64"

It worked. SVN is now up and running.

I read this post to figure it out

[davemac]

Finally, with some great help from someone on this post, I have finally got SVN working on Bluehost on a 64 bit box.

Here's the commands I used. Replace zzzzz with your username:

mkdir _src
cd _src
wget http://subversion.tigris.org/downloads/subversion-1.4.6.tar.gz
wget http://subversion.tigris.org/downloads/subversion-deps-1.4.6.tar.gz
tar -xzvf subversion-1.4.6.tar.gz
tar -xzvf subversion-deps-1.4.6.tar.gz
cd subversion-1.4.6
cd apr
./configure --enable-shared --prefix=$HOME
make && make install
cd ../apr-util
./configure --enable-shared --prefix=$HOME \
     --with-expat=builtin --with-apr=$HOME \
     --without-berlekey-db
make && make install
cd ../neon
EXTRA_CFLAGS="-L/usr/lib64 -fPIC"
CFLAGS="-L/usr/lib64 -fPIC"
./configure --prefix=/home/zzzzz/system --enable-shared
make && make install
cd ..
./configure --prefix=/home/zzzzz/system --with-expat=builtin
make && make install

Then you need to edit .bash_profile to add /system/bin to your path. From your home folder:

nano -w .bash_profile

replace:

PATH=$PATH:$HOME/bin

with:

PATH=$PATH:$HOME/bin:$HOME/system/bin

You will need to logout of your session, and then log in again. Subversion should now be working.

[MarcoBarbosa]

Hi there,

I'm aaaaaaaalmost 100% successfull with SVN+bluehost

I would really appreciate if you could give me any tips of how to reach my goal

My case:
- SVN installed
- Repository created and imported content from a dump file (<- i almost died here)
- I can update the content with success (another pain here with windows)

The thing is: when i change a file, and commit, with success, it doesn't really commit!
When i check in the server the file is unchanged

what could that be?
what step am i missing?
what's killing me is that i know it must be a detail!

i don't know if i get happy or worried that i get no erros, as i can update and commit correctly (in theory)