Subject: Re: configure with non standard openssl installation path

Re: configure with non standard openssl installation path

From: Bill Segall <>
Date: Tue, 24 May 2011 20:24:53 +1000

My configure line is:
./configure --build=x86_64-redhat-linux --host=mips64-octeon-linux-gnu
--with-openssl --enable-static --disable-shared

This reports:
checking for libssl... no
checking for libgcrypt... no
configure: error: cannot find OpenSSL or Libgcrypt,
try --with-libssl-prefix=PATH or --with-libgcrypt-prefix=PATH

That's the right path to my openssl build:

 $ ls /site/platforms/mips64-octeon-linux/stow/openssl-0.9.8r
bin/ include/ lib/ openssl/

config.log shows:
-o conftest -ggdb3 -O0 -Wall -Wextra conftest.c -lssl -lcrypto >&5
conftest.c:25:25: error: openssl/ssl.h: No such file or directory
configure:12975: $? = 1

Looking at my I see no sign of an AC_ARG_WITH(libssl-prefix)

Thanks for any help,

On Tue, May 24, 2011 at 5:22 PM, Simon Josefsson <>wrote:

> Bill Segall <> writes:
> > I'm endeavouring to cross-compile libssh2-1.2.8 but I don't see a valid
> > mechanism for telling configure the location of my openssl libraries.
> >
> > seems to understand a --with-openssl which tells it that I
> > should use that over gcrypt and it alludes to a --wtih-libssl-prefix=
> option
> > but that seems not to actually have been implemented. As I'm
> cross-compiling
> > libssh isn't going to be found in my system path.
> It is implemented. What are the commands you are using, and what error
> do you get?
> Normally you either use ./configure CPPFLAGS=foo LDFLAGS=bar to hard
> code library settings, but you can also use ./configure --with-openssl
> --with-libssl-prefix=/foo/bar/root/usr to do it in a platform
> independent way.
> /Simon
> _______________________________________________
> libssh2-devel

Received on 2011-05-24