www.libssh2.org | Daily snapshots | Mailing list archive | Docs | Examples | github

Archive Index This month's Index

Subject: [libssh2] #304: Improperly linking to system libssl & libcrypto when staged one is desired

[libssh2] #304: Improperly linking to system libssl & libcrypto when staged one is desired

From: libssh2 Trac <trac_at_libssh2.stuge.se>
Date: Thu, 21 May 2015 15:33:28 -0000

#304: Improperly linking to system libssl & libcrypto when staged one is desired
---------------------------+--------------------
 Reporter: kotoroshinoto | Owner:
     Type: defect | Status: new
 Priority: normal | Milestone: 1.5.0
Component: crypto | Version: 1.5.0
 Keywords: | Blocked By:
   Blocks: |
---------------------------+--------------------
 no matter what I do, it ends up linking to the system files:
 libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007f83a6248000)
 libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x00007f83a5e68000)

 it should be linking to the ones in
 ls /UCHC/HPC/Gooch/biotoolmodules/openssl/1.0.2a/lib/
 engines libcrypto.a libcrypto.so libcrypto.so.1.0.0 libssl.a libssl.so
 libssl.so.1.0.0 pkgconfig

 what do I need to tell the configure script to accomplish this?

-- 
Ticket URL: <https://trac.libssh2.org/ticket/304>
libssh2 <https://trac.libssh2.org/>
C library for writing portable SSH2 clients
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2015-05-21

the libssh2 team