It's recommended that recent versions of openssl be built only as static libraries because the ABIs are not yet stable (esp. the `engine' component). However, the library still uses dlopen. Linking openssh will therefore fail unless linking against -ldl explicitly along with -lcrypto. It should be harmless to do so when linking dynamically. Also, it would be useful if the configure script for openssh would check for the minimum version of openssl required. Version 0.9.5 did not define some functions that openssh wanted; I had to upgrade to 0.9.6.
On Wed, Mar 20, 2002 at 02:42:05PM -0800, Noah Friedman wrote:> It's recommended that recent versions of openssl be built only as static > libraries because the ABIs are not yet stable (esp. the `engine' > component). However, the library still uses dlopen.this depends on how you configure openssl.
On Wed, 20 Mar 2002, Noah Friedman wrote:> It's recommended that recent versions of openssl be built only as static > libraries because the ABIs are not yet stable (esp. the `engine' > component). However, the library still uses dlopen. > > Linking openssh will therefore fail unless linking against -ldl explicitly > along with -lcrypto. It should be harmless to do so when linking > dynamically.What platform are you on? What errors do you get? -- Tim Rice Multitalents (707) 887-1469 tim at multitalents.net
Seemingly Similar Threads
- building OpenSSH-3.1p1 w/OpenSSL-0.9.6d
- Compile of openssh 4.2 failed with openssl 0.9.8
- sshd 3.9p1 under Reliant Unix 5.45: getpeername: Operation not supported on transport endpoint
- openssh wish list for 2.6.*
- greater than 8 character passwords on Unixware (IA database support)