Subject: [libssh2] [ libssh2-Bugs-1837516 ] Cannot compile libssh2-0.14 on a Suse 10 Enterprise Server

[libssh2] [ libssh2-Bugs-1837516 ] Cannot compile libssh2-0.14 on a Suse 10 Enterprise Server

From: SourceForge.net <noreply_at_sourceforge.net>
Date: Tue, 27 Nov 2007 01:18:33 -0800

Bugs item #1837516, was opened at 2007-11-24 04:18
Message generated for change (Comment added) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=703942&aid=1837516&group_id=125852

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Cannot compile libssh2-0.14 on a Suse 10 Enterprise Server

Initial Comment:

Hi

I'm trying to compile libssh2-0.14 on a Suse 10 Enterprise Server updated to SP1,.

This is the error:

slc-107:/tmp/libssh2-0.14 # ./configure
> > > > > checking build system type... x86_64-unknown-linux-gnu
> > > > > checking host system type... x86_64-unknown-linux-gnu
> > > > > checking for gcc... gcc
> > > > > checking for C compiler default output file name... a.out
> > > > > checking whether the C compiler works... yes
> > > > > checking whether we are cross compiling... no
> > > > > checking for suffix of executables...
> > > > > checking for suffix of object files... o
> > > > > checking whether we are using the GNU C compiler... yes
> > > > > checking whether gcc accepts -g... yes
> > > > > checking for gcc option to accept ANSI C... none needed
> > > > > checking for socket in -lsocket... no
> > > > > checking for ceil in -lm... yes
> > > > > checking for gcc... (cached) gcc
> > > > > checking whether we are using the GNU C compiler... (cached) yes
> > > > > checking whether gcc accepts -g... (cached) yes
> > > > > checking for gcc option to accept ANSI C... (cached) none needed
> > > > > checking for a BSD-compatible install... /usr/bin/install -c
> > > > > checking whether ln -s works... yes
> > > > > checking whether make sets $(MAKE)... yes
> > > > > checking for ranlib... ranlib
> > > > > checking whether byte ordering is bigendian... no
> > > > > checking for pkg-config... no
> > > > > checking for OpenSSL... configure: error: Cannot find OpenSSL's
> > > libcrypto

I have installed openssl and openssl-devel packages and the libraries seems to be well linked:

slc-107:/tmp/libssh2-0.14 # ldconfig -v |grep libcrypto
> > > ldconfig: Can't stat /usr/X11R6/lib64/Xaw3d: No such file or directory
> > > ldconfig: Can't stat /usr/X11R6/lib/Xaw3d: No such file or directory
> > > ldconfig: Can't stat /opt/kde3/lib: No such file or directory
> > > ldconfig: Can't stat /opt/kde3/lib64: No such file or directory
> > > ldconfig: Path `/lib' given more than once
> > > ldconfig: Path `/lib64' given more than once
> > > ldconfig: Path `/usr/lib' given more than once
> > > ldconfig: Path `/usr/lib64' given more than once
> > > libcrypto.so.0.9.8 -> libcrypto.so.0.9.8
> > > libcrypto.so.0.9.7 -> libcrypto.so.0.9.7

I tried to compile the lastest version too but i had the same error.

In this machine i have compiled and installed nrpe (for example) that uses the same libraries without problems.

What can i do?

Thank you very much and sorry for my English ;-)

jmachr_at_hotmail.com

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2007-11-27 01:18

Message:
Logged In: NO

I tried to compiled with the --with-opensssl option, but it didn't work,
this is the new error:

checking for OpenSSL... Using explicit path /usr/include/openssl
configure: error: Missing one or more of <openssl/bn.h>, <openssl/evp.h>,
<openssl/hmac.h>, <openssl/pem.h>, <openssl/sha.h>

I checked that all the "missing" headers are in the path given.

This ocurred with both version of the library (14 and 18), and config.log
donĀ“t give more usefull information.

thanks

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2007-11-25 02:27

Message:
Logged In: NO

The reason for install an old version is that we have some programs
compiled to run with that library in an older machine, and we want to keep
the same configuration in both servers.

I have OpenSSL development package already install, so i'll try to compile
with the openssl option.

Thanks!!!

----------------------------------------------------------------------

Comment By: Dan Fandrich (dfandrich)
Date: 2007-11-24 11:13

Message:
Logged In: YES
user_id=236775
Originator: NO

Ah, I missed the line in the middle that said you tried the latest version
as well. It sounds like you might not have the OpenSSL development package
installed, or, if you do, use the --with-openssl option on configure to
point to its installation directory. If you still can't figure it out, look
at the config.log file and get some clues. Oh, and please stick with the
latest version!

----------------------------------------------------------------------

Comment By: Dan Fandrich (dfandrich)
Date: 2007-11-24 10:58

Message:
Logged In: YES
user_id=236775
Originator: NO

Version 0.14 is 4 versions out of date. Try ver. 0.18.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=703942&aid=1837516&group_id=125852

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
libssh2-devel mailing list
libssh2-devel_at_lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libssh2-devel
Received on 2007-11-27