Today I needed to take a Red Hat Linux box and get the Subversion client running on it so I could check out some source from a secure repository. Initially, building and installing Subversion was a snap using their latest tarball. However, all it took was an attempt to check out the source to see that my job was not quite done. After trying to run a command like the following:
svn co https://www.example.com/svn/trunk/source
I got the following error:
svn: SSL is not supported
Luckily it only took a quick Google search to find the source of my problem. I needed to compile Subversion against a version of neon that had SSL enabled.
So here's what I did. I downloaded the version of neon that is recommended by Subversion (since the latest version is apparently a little too recent to work with the latest version of Subversion). Then I did the typical ./configure, make, make install routine, with the following exception:
./configure --with-ssl
By adding the --with-ssl switch, I've ensured that neon will be compiled with SSL support turned on.
Then, I did a make clean on my previous Subversion compilation and reconfigured it to use the version of neon that I had just compiled, like so:
./configure --with-neon=/usr/local/
Note that I pointed to /usr/local/ because of another Subversion recommendation.
After reconfiguring, compiling and installing, I now have the Subversion client running on my Linux machine with SSL support enabled.
Comments
It was very useful to me: I overcome the obtrusive error
svn: SSL is not supported
My Linux is Slackware 10.1, obviously the build-in neon in the distribution is compiled without ssl.
Oooo, I forgot, the subversion client is very sensitive about Neon version. Check your INSTALL file for the needed version and download it, not newer, because it will give error on ./configure
thanks..
newbie to redhat.
that was a big help
Thanks for posting this page. Just one suggestion. When you mention that neon should be compiled with the --with-ssl switch added, you should add that this should be done as part of a separate install of neon. You can still keep neon as a dependency sub-directory of the subversion install directory (as it is now done as of subversion 1.4.x), but rather than just getting neon installed with the install of subversion, you should go through the steps of configuring and making neon from within the neon sub-directory first, THEN do the configure, make and make install for subversion itself. Maybe that's obvious to all others but it wasn't to me. Anyway, again, thanks.
Just thought I'd ad that if you want to install Neon with SSL in a non-standard location, use: (for example)
./configure CPPFLAGS="-I/home/svn/local/include" LDFLAGS="-L/home/svn/local/lib"
--prefix=/home/svn/local
--enable-shared
--with-ssl
This info is still valid. I just used it to compile and build svn latest 1.4.6 on RedHat Enterprise 4. Today is 5/4/2008.
Thank you for the post.
By the way, to remove the version of svn that comes with RedHat out of the box (1.1.4), you can use:
rpm -e subversion
Thanks again!
Scott, thanks for verifying that this still works with the latest version(s). That is pretty cool to know!
I have existing subversion 1.4.3 installation. Also there is libneon.a present in /usr/local/lib. Do i need to re-install SVN from source and configure it with neon? Or is there any way to extend existing SVN installation to use neon.
Suyash, don't consider this the definitive answer, but if I had to guess I'd say you probably have to rebuild Subversion configured with neon. You might do some research first, though. Good luck!
Excellent little tutorial. I used it in anger this morning.
For me, it was thus:
cd src/subversion-1.3.2
./configure --with-ssl
make -s && sudo make install
sudo apachectl graceful
Worked a treat!
Post Comments
If you feel like commenting on the above item, use the form below. Your email address will be used for personal contact reasons only, and will not be shown on this website.
Great!!
Permalink