When working with Subversion on older Linux distributions like RedHat 5, you might encounter the frustrating "Unrecognized URL scheme" error when trying to access repositories via HTTP/HTTPS. The root cause typically stems from missing or improperly configured neon library support during compilation.
From your configuration output, I notice several critical points:
configure: WARNING: unrecognized options: --with-ssl, --with-neon
configure: WARNING: we have configured without BDB filesystem support
This indicates the build system isn't properly recognizing your neon installation path. The make errors that follow suggest fundamental toolchain issues with libtool.
1. Verify Prerequisite Packages
First ensure all development tools are installed:
yum groupinstall "Development Tools"
yum install openssl-devel zlib-devel expat-devel
2. Proper Neon Configuration
The key is to point to neon's correct installation location:
./configure --prefix=/usr/local/subversion/ \
--with-apxs=/usr/local/subversion/bin/apxs \
--with-apr=/usr/local/subversion/bin/apr-1-config \
--with-apr-util=/usr/local/subversion/bin/apu-1-config \
--with-libs=/usr/local/ssl \
--with-neon=/u01/soft/neon-0.29.6
3. Fixing Libtool Issues
The make errors suggest libtool problems. Try regenerating build files:
make distclean
autoreconf -f -i
./configure [your options]
For more modern HTTP support, consider using serf instead of neon:
./configure --with-serf=/path/to/serf \
--with-apr=/usr/local/subversion/bin/apr-1-config \
--with-apr-util=/usr/local/subversion/bin/apu-1-config
After successful compilation, check RA modules:
svn --version
You should see ra_neon
or ra_serf
in the available modules list.
- Mixing 32-bit and 64-bit libraries
- Incorrect library paths in LD_LIBRARY_PATH
- Version conflicts between neon and subversion
Remember to backup your existing installation before making changes, and consider using a clean build environment if issues persist.
When attempting to use HTTP/HTTPS URLs with a custom-built Subversion (SVN) 1.8.0 installation on Red Hat Enterprise Linux 5, the system throws the error:
svn: E170000: Unrecognized URL scheme for httpxxxx
The key indicator comes from the svn --version
output showing missing HTTP/HTTPS modules:
The following repository access (RA) modules are available:
* ra_svn : handles 'svn' scheme
* ra_local : handles 'file' scheme
The initial configuration included neon library support:
./configure --prefix=/usr/local/subversion/ \
--with-apxs=/usr/local/subversion/bin/apxs \
--with-apr=/usr/local/subversion/bin/apr-1-config \
--with-apr-util=/usr/local/subversion/bin/apu-1-config \
--with-ssl --with-neon=/u01/soft/neon-0.29.6/
However, warnings appeared about unrecognized options:
configure: WARNING: unrecognized options: --with-ssl, --with-neon
The make process fails with multiple libtool errors:
/u01/soft/subversion-1.8.0/libtool: line 865: X--tag=CC: command not found
[...]
make: *** [subversion/libsvn_delta/cancel.lo] Error 1
Here's the complete step-by-step resolution:
1. Install Prerequisites
yum install -y gcc make openssl-devel
wget https://webdav.org/neon/neon-0.30.0.tar.gz
tar xzf neon-0.30.0.tar.gz
cd neon-0.30.0
./configure --prefix=/usr/local/neon --with-ssl
make
make install
2. Reconfigure Subversion
Modify the configure command to use correct parameters:
export LDFLAGS="-L/usr/local/neon/lib"
export CPPFLAGS="-I/usr/local/neon/include"
./configure --prefix=/usr/local/subversion/ \
--with-apxs=/usr/local/subversion/bin/apxs \
--with-apr=/usr/local/subversion/bin/apr-1-config \
--with-apr-util=/usr/local/subversion/bin/apu-1-config \
--with-serf=/usr/local/serf \
--with-ssl=openssl \
--enable-neon
3. Fixing libtool Issues
For the libtool errors, ensure proper environment:
export LIBTOOL="/usr/bin/libtool"
export LIBTOOLIZE="/usr/bin/libtoolize"
make clean
autoreconf -f -i
4. Complete Installation
make
make install
ldconfig
After successful installation, verify HTTP support:
svn --version | grep ra_
Should now show:
* ra_neon : Module for accessing a repository via WebDAV protocol (using neon).
- handles 'http' scheme
- handles 'https' scheme
- Ensure neon libraries are in /etc/ld.so.conf.d/
- Check for multiple libtool versions causing conflicts
- Verify openssl development packages are installed
- Consider newer versions (neon 0.30+ recommended)