RE: Compiling Subversion with SSL Support - not happening

Hi Stefen

This is what I did,

1. downloaded suberversion-1.5.4.tar.gz
2. unzipped the file
3. downloaded subversion-deps-1.5.4.tar.gz
4. unzipped this tar file in the same directory, where subversion is
unzipped
5. deleted "serf" directory
6. ran the following "configure" command
   ./configure
        --prefix=/ebay/software/pkgs/linux/2.4.21/i686/subversion/1.5.4/

        --without-apxs
        --with-ssl
        
--with-libs=/ebay/software/pkgs/linux/2.4.21/i686/openssl/0.9.8i/
        
--includedir=/ebay/software/pkgs/linux/2.4.21/i686/openssl/0.9.8i/includ
e
        --disable-shared
This resutls in this error,

config.status: creating subversion/svn_private_config.h
config.status: subversion/svn_private_config.h is unchanged
config.status: executing mkdir-init commands
configure: WARNING: Unrecognized options: --with-libs
configure: WARNING: we have configured without BDB filesystem support

I have attached the log files.

What is the right way to build svn with openssl support?

Thanks
nambi
 

-----Original Message-----
From: Stefan Sperling [mailto:stsp_at_elego.de]
Sent: Friday, December 12, 2008 5:26 PM
To: Sankaran, Nambi
Cc: users_at_subversion.tigris.org
Subject: Re: Compiling Subversion with SSL Support - not happening

On Fri, Dec 12, 2008 at 12:15:58PM -0800, Sankaran, Nambi wrote:
> Hi Stefan
>
> Thanks for looking into this issue.

> checking openssl/opensslv.h usability... no checking
> openssl/opensslv.h presence... no checking for openssl/opensslv.h...
> no
> configure: error: We require OpenSSL; try --with-openssl configure
> failed for serf
>

That error message is from serf's configure script.

> Since, the error message is "try --with-openssl", I tried the
> following command

The error message is misleading. The --with-openssl option is supposed
to be passed to the serf configure script, not Subversion's configure
script.

Are you sure you need serf? It is experimental. If you don't care about
which http access method you use, neon should be enough.
Neon and serf provide the same functionality.

If you're sure you need serf, have you read this part of Subversion's
INSTALL file? It says you should install serf before building
Subversion, and pass --with-serf option to Subversion's configure
script:

        b. Serf library 0.1.2 or newer (http://code.google.com/p/serf/)

           serf is a library for HTTP and WebDAV which is an
           alternative to Neon for accessing Subversion repositories
           over http:// and https:// URLs. serf is designed as an
           asynchronous library which can take advantage of HTTP
           pipelining, so ra_serf may be more efficient than ra_neon
           and better for HTTP proxy caches. The serf library can be
           found at:

               http://code.google.com/p/serf/

           In order to use ra_serf instead of ra_neon, you must install
           serf, and run Subversion's ./configure with the argument
           --with-serf. (To only use ra_serf and not ra_neon, you
           should also use --without-neon.) If serf is installed in a
           non-standard place, you should use

               --with-serf=/path/to/serf/install

           instead. If you build with both ra_neon and ra_serf,
           Subversion will use ra_neon by default; add "http-library =
           serf" to the [global] section of your ~/.subversion/servers
           file to use ra_serf instead.

           For more information on serf and Subversion's ra_serf, see
           the file subversion/libsvn_ra_serf/README.

Stefan

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=984611

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].