Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Problem installing openssh v2.9-p2 Post 5341 by htsubamoto on Friday 10th of August 2001 06:14:54 PM
Old 08-10-2001
Question Problem installing openssh v2.9-p2

I am trying to install openssh v2.9-p2 on Solaris 8. I already installed zlib and openssl, as required in INSTALL file. But when I issue ./configure to configure openssh v2.9-p2 for my platform ( I got the sources), it stops in the folowing message:

checking for OpenSSL directory... configure: error: Could not find working OpenSSL library, please install or check config.log

Looking in config.log file, I encountered the folowing message:

configure:4433: gcc -o conftest -g -O2 -Wall -I/opt -I/usr/local/include -I/usr/local/ssl/include -R/opt -L/opt -L/usr/local/lib -L/usr/local/ssl -L/export/home/gouvei/openssl/openssl-engine-0.9.6a -R/usr/local/lib conftest.c -lz -lsocket -lnsl -lgen -lcrypto 1>&5
Undefined first referenced
symbol in file
dlclose /export/home/gouvei/openssl/openssl-engine-0.9.6a/libcrypto.a(dso_dlfcn.o) (symbol belongs to implicit dependency /usr/lib/libdl.so.1)
dlsym /export/home/gouvei/openssl/openssl-engine-0.9.6a/libcrypto.a(dso_dlfcn.o) (symbol belongs to implicit dependency /usr/lib/libdl.so.1)
dlopen /export/home/gouvei/openssl/openssl-engine-0.9.6a/libcrypto.a(dso_dlfcn.o) (symbol belongs to implicit dependency /usr/lib/libdl.so.1)
ld: fatal: Symbol referencing errors. No output written to conftest
collect2: ld returned 1 exit status

I am using gcc v3.0. Does anybody knows what´s the problem? The zlib and ssl I installed from the sources ( I compiled them ) and everything went fine. Any help would be grateful.

TKS

HTT
 

10 More Discussions You Might Find Interesting

1. Solaris

Installing openSSH 3.5p1 on Solaris 5.6

Hello, I have installed OpenSSH_3.5p1 On Solaris 5.6. Specifically, I have installed these packages: OBSDssh-3.5p1-sparc-sun4u-5.6.pkg DJBdaemon-0.76-sparc-sun4u-5.6.pkg ANDIrand-0.7-sparc-sun4u-5.6.pkg All three packages have installed successfully. From this point, I can... (8 Replies)
Discussion started by: chucker8
8 Replies

2. SCO

Installing and using openSSH on SCO 5.0.6

I have a few resources that I have read that show what I need, openSSL and zlib of one version or another to get openSSH to work to start. Here is my dilemma to start, I will need to compile the source for the openSS* and the zlib, but when I type "make" into the command prompt I get "make: not... (8 Replies)
Discussion started by: PinkLemonade
8 Replies

3. Solaris

problem while installing on X-86

Hi all, I tried to install Sun Solaris 10 on a X-86 based machine. I have dedicated entire diskspace to create auto partition. My hardware config is below: Main Board : Asus Processor : Intel 945 , 3 G/Hz RAM : 1 Gigs Diskspace : 80 Gigs When I install, installation goes successful.... (1 Reply)
Discussion started by: naw_deepak
1 Replies

4. UNIX for Dummies Questions & Answers

A problem about openssh

When I first link a computer with ssh , the information "Warning: Permanently added ... (RSA) to the list of known hosts." will be occured. How can i avoid this information without use the parameter '-q'? tks!!! (2 Replies)
Discussion started by: ragehunter
2 Replies

5. AIX

AIX 6.1 - openssh - problem

Hello, I am new in aix unix. First i install openssl - success, next step i try install openssh when i put command geninstall -Y -d /myssh openssh.base i have this message: What is the problem? Thanks for help. Sorry for my bad english i still learning. ---------- Post updated at... (2 Replies)
Discussion started by: bieszczaders
2 Replies

6. Fedora

OpenSSH Problem

Hello, I cannot seem to loggon to a machine using ssh/scp. Whenevr I do it closes the connection (error message : lost connection)but it appears to be the host machine closing rather than the destination which puzzles me even more. What is even weirder is that as a root user it works but as a... (1 Reply)
Discussion started by: mojoman
1 Replies

7. UNIX for Advanced & Expert Users

Problem with OpenSSH Remote Port Forwarding with Bind_address

As in the ssh(1) man page: -R bind_address:]port:host:hostport .......By default, the listening socket on the server will be bound to the loopback interface only. This may be overridden by specifying a bind_address. An empty bind_address, or the address `*', indicates... (2 Replies)
Discussion started by: ahmad.zuhd
2 Replies

8. Shell Programming and Scripting

Problem with perl openssh

hello, can anyone help me with this problem? im just a beginner and currently starting to program in perl, also i just installed openssh because what i really need is to ssh to a ubuntu server. so I tried my code: #!/usr/bin/perl use strict; use warnings; use Net::OpenSHH; my $ssh =... (4 Replies)
Discussion started by: samohung390
4 Replies

9. Solaris

Problem installing companion CD

Hi everyone, Im very new to solaris and im trying to install the companion CD remotly via telent on my sunfire V120 server i have running. I download the iso off the net then burned it to cd. I have tried various how to's.. but its still not working.. The commands they tell me to imput come... (4 Replies)
Discussion started by: Smitty944
4 Replies

10. Red Hat

Installing OPENSSH 6.2P2 on RHEL 4, 64B failed

make: Leaving directory `/u01/openssh-6.2p2/openbsd-compat' gcc -g -O2 -Wall -Wpointer-arith -Wuninitialized -Wsign-compare -Wformat-security -fno-strict-aliasing -D_FORTIFY_SOURCE=2 -fno-builtin-memset -std=gnu99 -I. -I. -DSSHDIR=\"/usr/local/etc\" - D_PATH_SSH_PROGRAM=\"/usr/local/bin/ssh\"... (0 Replies)
Discussion started by: scao
0 Replies
COMPAT_30(8)						    BSD System Manager's Manual 					      COMPAT_30(8)

NAME
compat_30 -- setup procedure for backward compatibility on post-3.0 releases SYNOPSIS
options COMPAT_30 DESCRIPTION
The compat_30 module allows NetBSD to run NetBSD 3.0 executables. The support is present if the kernel was built with option COMPAT_30. It is not available as a loadable module. Static executables typically need no additional setup. Dynamic binaries may require shared libraries whose major version number changed since NetBSD 3.0, which are listed below. A shadow directory under /emul is not used; the libraries can be obtained from a NetBSD 3.0 dis- tribution and installed in the original directories shown, as the major version number in the file name will prevent conflicts. If an upgrade installation from NetBSD 3.0 has been done and these libraries are still present, nothing more need be done. Libraries needed from 3.0 /lib/libcrypto.so.2.1 /lib/libcrypto.so.2 /usr/lib/libcrypto.so.2.1 /usr/lib/libcrypto.so.2 /lib/libevent.so.0.2 /lib/libevent.so.0 /usr/lib/libevent.so.0.2 /usr/lib/libevent.so.0 /usr/lib/libg2c.so.2.0 /usr/lib/libg2c.so.2 /usr/lib/libkadm.so.5.0 /usr/lib/libkadm.so.5 /usr/lib/libkafs.so.6.0 /usr/lib/libkafs.so.6 /usr/lib/libkdb.so.5.0 /usr/lib/libkdb.so.5 /usr/lib/libkrb5.so.19.1 /usr/lib/libkrb5.so.19 /usr/lib/libkrb.so.6.0 /usr/lib/libkrb.so.6 /usr/lib/libkstream.so.2.0 /usr/lib/libkstream.so.2 /usr/lib/libmagic.so.0.1 /usr/lib/libmagic.so.0 /usr/lib/libpcap.so.1.4 /usr/lib/libpcap.so.1 /lib/libradius.so.0.0 /lib/libradius.so.0 /usr/lib/libradius.so.0.0 /usr/lib/libradius.so.0 /usr/lib/libssh.so.1.0 /usr/lib/libssh.so.1 /usr/lib/libssl.so.3.0 /usr/lib/libssl.so.3 /usr/lib/libstdc++.so.5.0 /usr/lib/libstdc++.so.5 /lib/libz.so.0.4 /lib/libz.so.0 /usr/lib/libz.so.0.4 /usr/lib/libz.so.0 /usr/lib/libamu.so.2.1 /usr/lib/libamu.so.2 IMPLEMENTATION NOTES
COMPAT_30 enables the NetBSD 3.0 versions of the following system calls, whose syscall numbers and argument structures were changed after the 3.0 release to accommodate 64-bit filesystems: fhstat(2), fstat(2), getdents(2), lstat(2), stat(2). The filehandle structure (formerly fhandle_t) was made opaque to userland and variable-sized. A fh_size argument was added to related syscalls: fhstat(2), fhstatvfs(2), fhstatvfs1(2), fhopen(2), getfh(2). This changes the API and ABI of those syscalls, COMPAT_30 enables binary compatibility with the old ABI. Source compatibility is not provided, as use of those syscalls is supposed to be rare. The error code from the socket(2) syscall changed from EPROTONOSUPPORT to EAFNOSUPPORT in the case of an unsupported address family. COMPAT_30 enables binary compatibility with the old ABI. Source compatiblility is not provided. The struct ntptimeval used by ntp_gettime(2) changed with the implementation of timecounters. SEE ALSO
config(1), fhstat(2), fstat(2), getdents(2), lstat(2), stat(2), options(4) HISTORY
NetBSD offers back-compatibility options back to NetBSD 0.9, but the first to be documented with a manual page is compat_30. BUGS
The compatible getdents(2) is unable to see directory entries beneath the top layer of a union, even though the real 3.0 getdents() did not have that problem. SECURITY CONSIDERATIONS
Programs with security impact that receive incorrect directory contents from getdents() may behave improperly, as when they are unable to find, or find the wrong versions of, important files. BSD
December 15, 2007 BSD
All times are GMT -4. The time now is 11:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy