Hi all:
I'm trying to compile OpenSSH 2.2.0p1 on an Origin 2000 running Irix
6.5.9 and when I run ./configure it didn't detect the OpenSSL libraries.
I compile/install OpenSSL 0.9.6. The installation was done using prefix
/usr/local/ssl. I test the binaries and they are working fine. Then,
when I try to configure the Openssh
./configure --prefix=/usr/local/ssh --with-ssl-dir=/usr/local/ssl
or
./configure --prefix=/usr/local/ssl --with-ssl-dir=/usr/local/ssl
or other options, I just get the message:
configure: error: Could not find working SSLeay / OpenSSL libraries,
please install
I add some "echo" on the configure script to see the differents paths
it
is testing and it is testing the correct ones at some point but it
doesn't detect it.
Any help will be welcome.
--William Caban
On Wed, 11 Oct 2000, William Caban wrote:> I compile/install OpenSSL 0.9.6. The installation was done using prefix > /usr/local/ssl. I test the binaries and they are working fine. Then, > when I try to configure the Openssh > > ./configure --prefix=/usr/local/ssl --with-ssl-dir=/usr/local/ssl > > or other options, I just get the message: > > configure: error: Could not find working SSLeay / OpenSSL libraries, > please installI assume the old version of OpenSSL you had installed is pre-0.9.5a. When you use --with-ssl-dir in OpenSSL, it'll first look at the standard directories, not the one specified. This has hit me a couple of times when you have an older version of OpenSSL in e.g. /usr/local/lib etc. -- you _can't_ override that easily.. AFAIR the order was changed in post-2.2.0p1 snapshots. -- Pekka Savola "Tell me of difficulties surmounted, Pekka.Savola at netcore.fi not those you stumble over and fall"
On Wed, Oct 11, 2000 at 02:43:38PM -0400, William Caban wrote:> Hi all: > > I'm trying to compile OpenSSH 2.2.0p1 on an Origin 2000 running Irix > 6.5.9 and when I run ./configure it didn't detect the OpenSSL libraries. > > I compile/install OpenSSL 0.9.6. The installation was done using prefix > /usr/local/ssl. I test the binaries and they are working fine. Then, > when I try to configure the Openssh > > ./configure --prefix=/usr/local/ssh --with-ssl-dir=/usr/local/ssl > or > ./configure --prefix=/usr/local/ssl --with-ssl-dir=/usr/local/ssl > > or other options, I just get the message: > > configure: error: Could not find working SSLeay / OpenSSL libraries, > please install > > I add some "echo" on the configure script to see the differents paths it > is testing and it is testing the correct ones at some point but it > doesn't detect it.Pekka Savola already commented on the possibility of an old SSL installation in the standard path. This however should not apply here. If there is a not-working OpenSSL, configure will go on to the next location, which would be the specified one. Anyway, configure logs everything it does (especially the failures) to config.log. Please check for the error message when examining /usr/local/ssl. Best regards, Lutz -- Lutz Jaenicke Lutz.Jaenicke at aet.TU-Cottbus.DE BTU Cottbus http://www.aet.TU-Cottbus.DE/personen/jaenicke/ Lehrstuhl Allgemeine Elektrotechnik Tel. +49 355 69-4129 Universitaetsplatz 3-4, D-03044 Cottbus Fax. +49 355 69-4153
Steve VanDevender wrote:> William Caban writes: > > > You shouldn't be using --prefix in that way. --prefix does not tell > > > configure where to find libraries; it tells configure where OpenSSH > > > will eventually be installed. > > > > Yes, I know. But when I look at the 'configure' script it also test for > > possible libraries on that direcotry and anyway, I was doing it to minimize > > any possible ($prefix)/lib missmatch, I just want to install it under > > /usr/local/ssh. > > > > > You may also need to add library path flags to your CFLAGS to tell your > > > C compiler where to find libraries; i.e. > > > > > > CFLAGS="-L/usr/local/lib -L/usr/local/ssl/lib" ./configure \ > > > --prefix=/usr/local --with-ssl-dir=/usr/local/ssl > > > > I try this but it is doing the same. Thanks anyway. > > In the general case, you need to determine where the OpenSSL includes > live, and if they are not in the default include path for your compiler, > add something like "-I/usr/local/ssl/include" to your CFLAGS. > Similarly, if the OpenSSL libraries are not in the default link path for > your compiler, you need to add something like "-L/usr/local/ssl/lib" to > your LDFLAGS. > > On some systems (i.e. Digital UNIX with the DEC C compiler) I have the > best luck with something like this: > > CC="cc -I/usr/local/include -L/usr/local/lib" CFLAGS="-O2" ./configure ... > > This is because not all configure tests actually pull in CFLAGS, but > they do pull in your definition of CC. > > If you dig around in config.log you might be able to determine which > configure test is failing and why, and adjust your invocation of > configure to match.Actually, thanks for that suggestion, I just look at the config.log and discover the real error: .... configure:2862: gcc -o conftest -L/usr/local/sshdist/lib -L/usr/local/sshdist/ssl/lib -I/usr/local/sshdist -I/usr/local/sshdist/ssl -I/usr/local/sshdist/incl 1219 ld: FATAL 12: Expecting 32-bit objects: /usr/local/sshdist/lib/libcrypto.a is 64-bit. configure: failed program was: ... This is happening for all the ssl tests so I have 32-bit binaries fighting with 64-bit binaries.... Nice jungle! Probably I could do it. Thanks! -------------- next part -------------- A non-text attachment was scrubbed... Name: william.vcf Type: text/x-vcard Size: 572 bytes Desc: Card for William Caban Url : http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20001011/7629192e/attachment.vcf