Error Compiling OpenSSH-3.4p1

Error Compiling OpenSSH-3.4p1

[Linux User]

Folks,
	Need a bit of help here as I try to move from rote user to semi-competent 
admin. I've got my internal server working, although it's rather crufty, as I 
just dumped things on it and bashed about til it worked. Now I'm trying to 
build a replacement up cleanly from the start, but I can't get past the first 
steps.

	I've started with a fairly empty installation of RH 6.2 (for various 
reasons, I'm NOT going with the latest/greatest). By "empty" I mean I did not 
install most packages, because I want to install the most recent versions 
from source. 

	First step is to get secure login via OpenSSH, so I can finish work from my 
desktop machine instead of the console. I've installed OpenSSL-0.9.6d, in the 
default directory (/usr/local/ssl), with shared libraries enabled. Next step 
was _supposed_ to be OpenSSH-3.4p1 (btw, _not_ the compromised one that was 
briefly on the main site ...). Unfortunately, configure keeps telling me my 
OpenSSL headers don't match my libraries, which I don't understand. The only 
headers on the system should be the ones with the libraries I just 
compiled--I did *not* install the default RH6.2 packages, so there are no old 
files or directories from previous versions laying around. I don't know what 
default directory OpenSSH assumes, so I tried specifying various directories 
as well, using the following commands:

	./configure
	./configure --with-ssl-dir=/usr/local/ssl
	./configure --with-ssl-dir=/usr/local/ssl/lib

	Nada.

	Any suggestions?(1) Should I go through and delete all the OpenSSL files, 
and reinstall in something OTHER than the default directory? I notice on my 
other machines that RedHat, for example, does NOT use the default directory. 
That always bothered me, because that makes it frustrating to install new 
versions the way the author actually intended. If you aren't careful, you (or 
at least I) wind up executing the old binary because it came first in the 
path, and then having to hunt down and delete leftovers.  But maybe there was 
 a reason RH did it that way.

(1) Please--no rants or tirades about using different distributions. Not 
interested at the moment.

Re: Error Compiling OpenSSH-3.4p1

[Camelia NASTASE]

>
> 	First step is to get secure login via OpenSSH, so I can finish work from my
> desktop machine instead of the console. I've installed OpenSSL-0.9.6d, in the
> default directory (/usr/local/ssl), with shared libraries enabled. Next step
> was _supposed_ to be OpenSSH-3.4p1 (btw, _not_ the compromised one that was
> briefly on the main site ...). Unfortunately, configure keeps telling me my
> OpenSSL headers don't match my libraries, which I don't understand. The only
> headers on the system should be the ones with the libraries I just
> compiled--I did *not* install the default RH6.2 packages, so there are no old
> files or directories from previous versions laying around. I don't know what
> default directory OpenSSH assumes, so I tried specifying various directories
> as well, using the following commands:
>
> 	./configure
> 	./configure --with-ssl-dir=/usr/local/ssl
> 	./configure --with-ssl-dir=/usr/local/ssl/lib
>
> 	Nada.


could you send the error you get?



have a nice day,
camelia
-- 
Camelia Nastase
Administrator Retea
Departamentul Internet
ASTRAL TELECOM SA, Sucursala Bucuresti
Tel: 021-3209204 Fax: 021-3209203

Re: Error Compiling OpenSSH-3.4p1

[Linux User]

On Saturday 03 August 2002 03:06 am, Camelia NASTASE wrote:
> could you send the error you get?

The specific error is "configure: error: Your OpenSSL headers do not match 
your library"

Checking through config.log, I find the following snippet. Note that it *is* 
correctly referencing the SSL include and library folders, and  the file 
librypto.so..0.9.61 *do* exist, and it *is* readable by root.

===== begin snip 
configure:8228: gcc -o conftest -g -O2 -Wall -Wpointer-arith 
-Wno-uninitialized -I/usr/local/ssl/include  -L/usr/local/ssl/lib  conftest.c 
-lutil -lz -lnsl  -lcrypto >&5
configure:8228: $? = 0
configure:8228: test -s conftest
configure:8228: $? = 0
configure:8233: checking whether OpenSSL's headers match the library
configure:8279: gcc -o conftest -g -O2 -Wall -Wpointer-arith 
-Wno-uninitialized -I/usr/local/ssl/include  -L/usr/local/ssl/lib  conftest.c 
-lutil -lz -lnsl  -lcrypto >&5
configure: In function `main':
configure:8283: warning: implicit declaration of function `SSLeay'
configure:8279: $? = 0
configure:8279: ./conftest
./conftest: error in loading shared libraries: libcrypto.so.0.9.6: cannot 
open shared object file: No such file or directory
configure:8279: $? = 127
configure: program exited with status 127
configure: failed program was:
#line 8279 "configure"
#include "confdefs.h"

#include <string.h>
#include <openssl/opensslv.h>
int main(void) { return(SSLeay() == OPENSSL_VERSION_NUMBER ? 0 : 1); }

configure:8279: result: no
configure:8279: error: Your OpenSSL headers do not match your library
===== end snip

Re: Error Compiling OpenSSH-3.4p1

[Linux User]

Please pardon my typographical errors ... I was mistakenly trying to 
multitask and using multiple computers via KVM at once. 

On Sunday 04 August 2002 09:58 am, Linux User wrote:
> On Saturday 03 August 2002 03:06 am, Camelia NASTASE wrote:
> > could you send the error you get?
>
> The specific error is "configure: error: Your OpenSSL headers do not match
> your library"
>
> Checking through config.log, I find the following snippet. Note that it
> *is* correctly referencing the SSL include and library folders, and  the
> file librypto.so.0.9.6 *does* exist, and it *is* readable by root.
>
> ===== begin snip
> configure:8228: gcc -o conftest -g -O2 -Wall -Wpointer-arith
> -Wno-uninitialized -I/usr/local/ssl/include  -L/usr/local/ssl/lib 
> conftest.c -lutil -lz -lnsl  -lcrypto >&5
> configure:8228: $? = 0
> configure:8228: test -s conftest
> configure:8228: $? = 0
> configure:8233: checking whether OpenSSL's headers match the library
> configure:8279: gcc -o conftest -g -O2 -Wall -Wpointer-arith
> -Wno-uninitialized -I/usr/local/ssl/include  -L/usr/local/ssl/lib 
> conftest.c -lutil -lz -lnsl  -lcrypto >&5
> configure: In function `main':
> configure:8283: warning: implicit declaration of function `SSLeay'
> configure:8279: $? = 0
> configure:8279: ./conftest
> ./conftest: error in loading shared libraries: libcrypto.so.0.9.6: cannot
> open shared object file: No such file or directory
> configure:8279: $? = 127
> configure: program exited with status 127
> configure: failed program was:
> #line 8279 "configure"
> #include "confdefs.h"
>
> #include <string.h>
> #include <openssl/opensslv.h>
> int main(void) { return(SSLeay() == OPENSSL_VERSION_NUMBER ? 0 : 1); }
>
> configure:8279: result: no
> configure:8279: error: Your OpenSSL headers do not match your library
> ===== end snip
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Error Compiling OpenSSH-3.4p1

[David J. Golden]

Just as an update, I tried deleting /usr/local/src/openssl-0.9.6d and 
/usr/local/ssl, and reinstalling. Still no joy. OpenSSH refuses configure. 
What is wrong here?

Re: Error Compiling OpenSSH-3.4p1

[Jeff Hunter]

Are you sure you have a non-compromised source package? Did you check 
the MD5 checksums against OpenSSH?

Jeff

David J. Golden wrote:
> Just as an update, I tried deleting /usr/local/src/openssl-0.9.6d and 
> /usr/local/ssl, and reinstalling. Still no joy. OpenSSH refuses configure. 
> What is wrong here?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: Error Compiling OpenSSH-3.4p1

[Linux User]

On Monday 05 August 2002 08:20 pm, Jeff Hunter wrote:
> Are you sure you have a non-compromised source package? Did you check
> the MD5 checksums against OpenSSH?

	Again, yes. Not only did I download it some time before the OpenSSH package 
was compromised, but I re-verified it after hearing of the compromise.

Re: Error Compiling OpenSSH-3.4p1

[Linux User]

Here's an update from my ongoing blind flailing in an attempt to get this to 
work:

PREFACE
========
- Before anybody else asks, NO, THIS IS NOT THE COMPROMISED VERSION! Sorry, 
but nobody seemed to get that the first time through, and I'm tired of 
repeating it.
- There are NO other header or library files laying around. I did NOT install 
the original RH6.2 rpms for OpenSSL or OpenSSH, and I verified that there 
were no same-name files hiding elsewhere on the path, or anywhere else on the 
filesystem.

INITIAL ATTEMPT: OpenSSL 0.9.6d, OpenSSH 3.4p1
=========================================
- OpenSSL 0.9.6d compiled fine with the 'shared' option
- OpenSSH 3.4p1 configure script bombed out configure: error: Your OpenSSL 
headers do not match your library.
    -- The headers are in the right place: /usr/local/ssl/include/openssl
    -- The libraries are all in the right place: /usr/local/ssl/lib
    -- The version in /usr/local/ssl/include/openssl/opensslv.h matches the 
library
    -- The openssl binary shows the correct version number
- Reading through the config.log file generated shows the following lines:

	configure:8279: gcc -o conftest -g -O2 -Wall -Wpointer-arith
	-Wno-uninitialized -I/usr/local/ssl/include  -L/usr/local/ssl/lib 
	conftest.c -lutil -lz -lnsl  -lcrypto >&5
	configure: In function `main':
	configure:8283: warning: implicit declaration of function `SSLeay'
	configure:8279: $? = 0
	configure:8279: ./conftest
	./conftest: error in loading shared libraries: libcrypto.so.0.9.6: cannot
	open shared object file: No such file or directory
	configure:8279: $? = 127
	configure: program exited with status 127
	configure: failed program was:
	#line 8279 "configure"
	#include "confdefs.h"

	#include <string.h>
	#include <openssl/opensslv.h>
	int main(void) { return(SSLeay() == OPENSSL_VERSION_NUMBER ? 0 : 1); }
	
	configure:8279: result: no
	configure:8279: error: Your OpenSSL headers do not match your library

	-- Note the include path specified: /usr/local/ssl/include. This is correct. 
The specific file included, openssl/opensslv.h, is under that path, and 
contains the correct version number.
	-- Note the library path specified: /usr/local/ssl/lib. This is also 
correct. The library which allegedly cannot be opened, libcrypto.so.0.9.6, is 
there, owner/group root, permissions -r-xr-xr-x.

So ... the files are there, the versions are correct, but the configure 
script cannot seem to load the shared library and hence claims the versions 
DON'T match. Why?

ADDITIONAL ATTEMPTS: OpenSSL 0.9.6e, various install paths
- Tried explicitly specifying the path to OpenSSL using 
"--with-ssl-dir=/usr/local/ssl" and got the same results
- Installed OpenSSL 0.9.6e, got the same results
- Tried installing OpenSSL in /usr/local and specifying the path with 
"-with-ssl-dir=/usr/local", got the same results.
- I even tried cutting the conftest.c file listed above out and manually 
compiling it.

So ... what am I doing wrong? How else can I troubleshoot this? I'm confused 
here! HELP!

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Error Compiling OpenSSH-3.4p1

[David Jackson]

Dude --
Is there a include path flag you can set with the ./configure?
Have you posted to a Redhat specific list? Have you search the Rehat 
archive for releated post?
Have you posted to openssl and openssh mailing list? Have you searched 
openssl and openssh archives?

David

Linux User wrote:

>Here's an update from my ongoing blind flailing in an attempt to get this to 
>work:
>
>PREFACE
>========
>- Before anybody else asks, NO, THIS IS NOT THE COMPROMISED VERSION! Sorry, 
>but nobody seemed to get that the first time through, and I'm tired of 
>repeating it.
>- There are NO other header or library files laying around. I did NOT install 
>the original RH6.2 rpms for OpenSSL or OpenSSH, and I verified that there 
>were no same-name files hiding elsewhere on the path, or anywhere else on the 
>filesystem.
>
>INITIAL ATTEMPT: OpenSSL 0.9.6d, OpenSSH 3.4p1
>=========================================
>- OpenSSL 0.9.6d compiled fine with the 'shared' option
>- OpenSSH 3.4p1 configure script bombed out configure: error: Your OpenSSL 
>headers do not match your library.
>    -- The headers are in the right place: /usr/local/ssl/include/openssl
>    -- The libraries are all in the right place: /usr/local/ssl/lib
>    -- The version in /usr/local/ssl/include/openssl/opensslv.h matches the 
>library
>    -- The openssl binary shows the correct version number
>- Reading through the config.log file generated shows the following lines:
>
>	configure:8279: gcc -o conftest -g -O2 -Wall -Wpointer-arith
>	-Wno-uninitialized -I/usr/local/ssl/include  -L/usr/local/ssl/lib 
>	conftest.c -lutil -lz -lnsl  -lcrypto >&5
>	configure: In function `main':
>	configure:8283: warning: implicit declaration of function `SSLeay'
>	configure:8279: $? = 0
>	configure:8279: ./conftest
>	./conftest: error in loading shared libraries: libcrypto.so.0.9.6: cannot
>	open shared object file: No such file or directory
>	configure:8279: $? = 127
>	configure: program exited with status 127
>	configure: failed program was:
>	#line 8279 "configure"
>	#include "confdefs.h"
>
>	#include <string.h>
>	#include <openssl/opensslv.h>
>	int main(void) { return(SSLeay() == OPENSSL_VERSION_NUMBER ? 0 : 1); }
>	
>	configure:8279: result: no
>	configure:8279: error: Your OpenSSL headers do not match your library
>
>	-- Note the include path specified: /usr/local/ssl/include. This is correct. 
>The specific file included, openssl/opensslv.h, is under that path, and 
>contains the correct version number.
>	-- Note the library path specified: /usr/local/ssl/lib. This is also 
>correct. The library which allegedly cannot be opened, libcrypto.so.0.9.6, is 
>there, owner/group root, permissions -r-xr-xr-x.
>
>So ... the files are there, the versions are correct, but the configure 
>script cannot seem to load the shared library and hence claims the versions 
>DON'T match. Why?
>
>ADDITIONAL ATTEMPTS: OpenSSL 0.9.6e, various install paths
>- Tried explicitly specifying the path to OpenSSL using 
>"--with-ssl-dir=/usr/local/ssl" and got the same results
>- Installed OpenSSL 0.9.6e, got the same results
>- Tried installing OpenSSL in /usr/local and specifying the path with 
>"-with-ssl-dir=/usr/local", got the same results.
>- I even tried cutting the conftest.c file listed above out and manually 
>compiling it.
>
>So ... what am I doing wrong? How else can I troubleshoot this? I'm confused 
>here! HELP!
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-admin" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>  
>

Re: Error Compiling OpenSSH-3.4p1

[Linux User]

On Tuesday 06 August 2002 02:33 pm, David Jackson wrote:
> Dude --
> Is there a include path flag you can set with the ./configure?

	Not quite--you can specify the top-level ssl directory using "with-ssl-dir=" 
and "include/" is assumed to be under that. I've tried both with and without, 
with OpenSSL in both standard and non-standard locations, to no avail.  And 
as near as I can tell, that's irrelevant anyway. The config log snippet 
*shows* it's using the correct include path.

> Have you posted to a Redhat specific list? Have you search the Rehat
> archive for releated post?

	No, because I'm not using RedHat RPMs. And not specifically; instead, I've 
done a general search of the web, including mailing lists (RedHat, openssl, 
openssh, and any others Google might index).

> Have you posted to openssl and openssh mailing list? Have you searched
> openssl and openssh archives?

	Not yet. I was hoping to avoid subscribing to Yet Another Mailing list, but 
that's my next step.

Re: Error Compiling OpenSSH-3.4p1

[David Jackson]

Linux User wrote:

>On Tuesday 06 August 2002 02:33 pm, David Jackson wrote:
>  
>
>>Dude --
>>Is there a include path flag you can set with the ./configure?
>>    
>>
>
>	Not quite--you can specify the top-level ssl directory using "with-ssl-dir=" 
>and "include/" is assumed to be under that. I've tried both with and without, 
>with OpenSSL in both standard and non-standard locations, to no avail.  And 
>as near as I can tell, that's irrelevant anyway. The config log snippet 
>*shows* it's using the correct include path.
>
>  
>
>>Have you posted to a Redhat specific list? Have you search the Rehat
>>archive for releated post?
>>    
>>
>
>	No, because I'm not using RedHat RPMs. And not specifically; instead, I've 
>done a general search of the web, including mailing lists (RedHat, openssl, 
>openssh, and any others Google might index).
>
>  
>
>>Have you posted to openssl and openssh mailing list? Have you searched
>>openssl and openssh archives?
>>    
>>
>
>	Not yet. I was hoping to avoid subscribing to Yet Another Mailing list, but 
>that's my next step.
>
>
>  
>
find on myh RH7.2 machine returns this:

bowtie: root >> find /lib /usr/lib -name "*ssl*" -exec ls -l {} \;
lrwxrwxrwx    1 root     root           16 Jun  5 18:58 /lib/libssl.so.2 
-> libssl.so.0.9.6b
-rwxr-xr-x    1 root     root       207036 Sep  7  2001 
/lib/libssl.so.0.9.6b
-rw-r--r--    1 root     root       273850 Sep  7  2001 /usr/lib/libssl.a
lrwxrwxrwx    1 root     root           26 Jun  5 19:10 
/usr/lib/libssl.so -> ../../lib/libssl.so.0.9.6b

If  "we" run ./configure --with-ssl=/usr/local/ssl   for openssh-3.4p1 
 by default it going to use the ld.so.conf file to search for libs? What 
maybe  happening is openssh configure is looking at the libssl in /lib 
or /usr/lib, and the headers under /usr/local/ssl?

One other note, I just build  openssl-0.9.6e using --prefix=/usr/local 
and it put the include under /user/local/include/openssl
and the libs under /usre/local/lib? You may have to use the 
--with-includedir=/usr/local/include/openssl with ssh?

David

Re: Error Compiling OpenSSH-3.4p1

[David Jackson]

David Jackson wrote:

> Linux User wrote:
>
>> On Tuesday 06 August 2002 02:33 pm, David Jackson wrote:
>>  
>>
>>> Dude --
>>> Is there a include path flag you can set with the ./configure?
>>>   
>>
>>
>>     Not quite--you can specify the top-level ssl directory using 
>> "with-ssl-dir=" and "include/" is assumed to be under that. I've 
>> tried both with and without, with OpenSSL in both standard and 
>> non-standard locations, to no avail.  And as near as I can tell, 
>> that's irrelevant anyway. The config log snippet *shows* it's using 
>> the correct include path.
>>
>>  
>>
>>> Have you posted to a Redhat specific list? Have you search the Rehat
>>> archive for releated post?
>>>   
>>
>>
>>     No, because I'm not using RedHat RPMs. And not specifically; 
>> instead, I've done a general search of the web, including mailing 
>> lists (RedHat, openssl, openssh, and any others Google might index).
>>
>>  
>>
>>> Have you posted to openssl and openssh mailing list? Have you searched
>>> openssl and openssh archives?
>>>   
>>
>>
>>     Not yet. I was hoping to avoid subscribing to Yet Another Mailing 
>> list, but that's my next step.
>>
>>
>>  
>>
> find on myh RH7.2 machine returns this:
>
> bowtie: root >> find /lib /usr/lib -name "*ssl*" -exec ls -l {} \;
> lrwxrwxrwx    1 root     root           16 Jun  5 18:58 
> /lib/libssl.so.2 -> libssl.so.0.9.6b
> -rwxr-xr-x    1 root     root       207036 Sep  7  2001 
> /lib/libssl.so.0.9.6b
> -rw-r--r--    1 root     root       273850 Sep  7  2001 /usr/lib/libssl.a
> lrwxrwxrwx    1 root     root           26 Jun  5 19:10 
> /usr/lib/libssl.so -> ../../lib/libssl.so.0.9.6b
>
> If  "we" run ./configure --with-ssl=/usr/local/ssl   for openssh-3.4p1 
> by default it going to use the ld.so.conf file to search for libs? 
> What maybe  happening is openssh configure is looking at the libssl in 
> /lib or /usr/lib, and the headers under /usr/local/ssl?
>
> One other note, I just build  openssl-0.9.6e using --prefix=/usr/local 
> and it put the include under /user/local/include/openssl
> and the libs under /usre/local/lib? You may have to use the 
> --with-includedir=/usr/local/include/openssl with ssh?
>
> David
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
This seemed to work except for this errror "sshd" prevledged user (which 
both sshd user and group exist):

OpenSSL:
/config --openssldir=/usr/local/ssl
make
make test
make install

OpenSSH:
/configure --prefix=/usr/local/ssh --with-ssl-dir=/usr/local/ssl   
--with-pam --with-md5-passwords
make all
make install

You will also need to adjust /etc/init.d/sshd script.

David

Re: Error Compiling OpenSSH-3.4p1

[Linux User]

On Tuesday 06 August 2002 06:31 pm, David Jackson wrote:
> This seemed to work except for this errror "sshd" prevledged user (which
> both sshd user and group exist):
>
> OpenSSL:
> /config --openssldir=/usr/local/ssl
> make
> make test
> make install
>
> OpenSSH:
> /configure --prefix=/usr/local/ssh --with-ssl-dir=/usr/local/ssl
> --with-pam --with-md5-passwords
> make all
> make install
>
> You will also need to adjust /etc/init.d/sshd script.

Sorry, I've already tried those exact commands. Repeatedly. No joy.

Re: Error Compiling OpenSSH-3.4p1

[Linux User]

On Tuesday 06 August 2002 06:00 pm, David Jackson wrote:
> find on myh RH7.2 machine returns this:
>
> bowtie: root >> find /lib /usr/lib -name "*ssl*" -exec ls -l {} \;
> lrwxrwxrwx    1 root     root           16 Jun  5 18:58 /lib/libssl.so.2
> -> libssl.so.0.9.6b

	It returns nothing on my, because, again, I did *not* install the OpenSSL 
RPMs that came with RedHat. I'm trying to install this on a "bare" machine 
that has never had either OpenSSL or OpenSSH installed. I have repeatedly 
verified that there are no other copies of either the binaries or the include 
files anywhere on the system.

> If  "we" run ./configure --with-ssl=/usr/local/ssl   for openssh-3.4p1
>  by default it going to use the ld.so.conf file to search for libs? What
> maybe  happening is openssh configure is looking at the libssl in /lib
> or /usr/lib, and the headers under /usr/local/ssl?

	That is *not* what is happening. As noted in my last email, the configure 
script **IS** using the correct paths for both headers and libraries.

> --with-includedir=/usr/local/include/openssl with ssh?

	I have done this as well. No difference.

Re: Error Compiling OpenSSH-3.4p1

[Glynn Clements]

Linux User wrote:

> Here's an update from my ongoing blind flailing in an attempt to get this to 
> work:
> 
> PREFACE
> ========
> - Before anybody else asks, NO, THIS IS NOT THE COMPROMISED VERSION! Sorry, 
> but nobody seemed to get that the first time through, and I'm tired of 
> repeating it.
> - There are NO other header or library files laying around. I did NOT install 
> the original RH6.2 rpms for OpenSSL or OpenSSH, and I verified that there 
> were no same-name files hiding elsewhere on the path, or anywhere else on the 
> filesystem.
> 
> INITIAL ATTEMPT: OpenSSL 0.9.6d, OpenSSH 3.4p1
> =========================================
> - OpenSSL 0.9.6d compiled fine with the 'shared' option
> - OpenSSH 3.4p1 configure script bombed out configure: error: Your OpenSSL 
> headers do not match your library.
>     -- The headers are in the right place: /usr/local/ssl/include/openssl
>     -- The libraries are all in the right place: /usr/local/ssl/lib

Can the loader find the libraries? I suspect not.

Either:

1. /usr/local/ssl/lib must be in $LD_LIBRARY_PATH, or

2. Both:
a) /usr/local/ssl/lib must be in /etc/ld.so.conf, and
b) ldconfig must have been run since a) was first true.

[IOW, "1 OR (2a AND 2b)"]

Note that the issue of whether or not the loader (/lib/ld-linux.so)
can find the shared libraries is a separate issue to whether or not
the linker (/usr/bin/ld, run from gcc) can find them.

BTW, this would normally be documented in the ld.so(8) manpage, but
that is very out of date (i.e. it documents the libc4 version, which
is prehistoric).

>     -- The version in /usr/local/ssl/include/openssl/opensslv.h matches the library
>     -- The openssl binary shows the correct version number
> - Reading through the config.log file generated shows the following lines:
> 
> 	configure:8279: gcc -o conftest -g -O2 -Wall -Wpointer-arith
> 	-Wno-uninitialized -I/usr/local/ssl/include  -L/usr/local/ssl/lib 
> 	conftest.c -lutil -lz -lnsl  -lcrypto >&5
> 	configure: In function `main':
> 	configure:8283: warning: implicit declaration of function `SSLeay'
> 	configure:8279: $? = 0

> 	configure:8279: ./conftest
> 	./conftest: error in loading shared libraries: libcrypto.so.0.9.6: cannot
> 	open shared object file: No such file or directory

This is what's important.

> 	configure:8279: $? = 127
> 	configure: program exited with status 127
> 	configure: failed program was:
> 	#line 8279 "configure"
> 	#include "confdefs.h"
> 
> 	#include <string.h>
> 	#include <openssl/opensslv.h>
> 	int main(void) { return(SSLeay() == OPENSSL_VERSION_NUMBER ? 0 : 1); }
> 	
> 	configure:8279: result: no
> 	configure:8279: error: Your OpenSSL headers do not match your library

This error message is incorrect. What it really means is "the test
program (which is meant to check that your OpenSSL headers match your
library) failed for some reason".

In this case, it failed because the loader failed to load a required
shared library.

> 	-- Note the include path specified: /usr/local/ssl/include. This is correct. 
> The specific file included, openssl/opensslv.h, is under that path, and 
> contains the correct version number.
> 	-- Note the library path specified: /usr/local/ssl/lib. This is also 
> correct. The library which allegedly cannot be opened, libcrypto.so.0.9.6, is 
> there, owner/group root, permissions -r-xr-xr-x.
> 
> So ... the files are there, the versions are correct, but the configure 
> script cannot seem to load the shared library and hence claims the versions 
> DON'T match. Why?

See above.

Suggested fix: add "/usr/local/lib" to /etc/ld.so.conf, then run
"ldconfig". Re-run ldconfig whenever you install new shared libraries.

-- 
Glynn Clements <glynn.clements@virgin.net>
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Error Compiling OpenSSH-3.4p1

[Linux User]

On Tuesday 06 August 2002 05:27 pm, Glynn Clements wrote:

> Suggested fix: add "/usr/local/lib" to /etc/ld.so.conf, then run
> "ldconfig". Re-run ldconfig whenever you install new shared libraries.

	Thanks! I'll take a swing at it tonight after work, and let you know how it 
went.

Re: Error Compiling OpenSSH-3.4p1

[David J. Golden]

On Tuesday 06 August 2002 05:27 pm, Glynn Clements wrote:
> Linux User wrote:
> > Here's an update from my ongoing blind flailing in an attempt to get this
> > to work:

> Can the loader find the libraries? I suspect not.
>
> Either:
>
> 1. /usr/local/ssl/lib must be in $LD_LIBRARY_PATH, or
>
> 2. Both:
> a) /usr/local/ssl/lib must be in /etc/ld.so.conf, and
> b) ldconfig must have been run since a) was first true.
>
> [IOW, "1 OR (2a AND 2b)"]

	Thanks! I finally managed to steal twenty minutes out of wedding 
preparations to test it , and that's what the problem was.