Subject: Re: Libssh2 make error.

Re: Libssh2 make error.

From: V, AnilKumar <>
Date: Wed, 18 Apr 2012 11:53:30 +0000

Hi ,

Now I'm able to configure for libssh2 package. But while doing the "make" step I was getting some symbol reference errors .

I think it is using openssl libraries, I have mentioned the path for openssl while configuring libssh2 but its not effecting.

Please find the attachment for config.log and make output.

Kindly help me.

Thanks And Regards,
Anil Kumar.V

-----Original Message-----
From: V, AnilKumar
Sent: Monday, April 16, 2012 2:32 PM
To: libssh2 development
Subject: RE: Reg: Getting error while configuring libssh2 package.


I tried with the latest version libssh2 1.4.1,but still getting the same error.

Please find the attached docs.

Thanks & Regards,
V. Anil Kumar.

-----Original Message-----
From: [] On Behalf Of Peter Stuge
Sent: Saturday, April 14, 2012 8:32 PM
Subject: Re: Reg: Getting error while configuring libssh2 package.

V, AnilKumar wrote:
> ./configure CC=cc CFLAGS=-xarch=v9 \
> --prefix=/ctxtools/cortex/local/64bit \
> --disable-shared --enable-static \
> --with-openssl --without-libgcrypt \
> --with-libssl-prefix=/ctxtools/cortex/local/64bit/ \
> --with-libz-prefix=/ctxtools/cortex/local/64bit
> I am sure openssl was present in this path "/ctxtools/cortex/local/64bit/ ".

> configure:2946: checking libssh2 version
> configure:2948: result: 1.2.4

Why are you using code which is more than two years old? You will not really get help unless you use the latest code.

> configure:12952: checking for libssl
> configure:12971: cc -o conftest -xarch=v9 conftest.c -lnsl -lsocket -lssl -lcrypto >&5
> "conftest.c", line 29: cannot find include file: <openssl/ssl.h>
> cc: acomp failed for conftest.c
> configure:12971: $? = 2

The error message is quite obvious.

You should look into why your prefix isn't in that command line. If you don't know where to start then try again with the latest code and send your configure command together with full output from running configure, as well as config.log.


The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.


Received on 2012-04-18