make tests failures (agent.sh)
scott rankin
waspswarm at gmail.com
Wed May 18 15:55:53 EST 2005
Hello,
I recently setup a CentOS 4.0 box (a derivative of RH).
I downloaded a 4.0p1 tarball of OpenSSH and grabbed OpenSSL 0.9.7e. I
configured OpenSSL with,
$ ./Configure no-idea no-rc5 shared linux-pentium
and it built fine. I didn't do a make install.
I then configured OpenSSH.
Here is a snippet of config.log:
[scott at choke openssh-4.0p1]$ less config.log
...
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by OpenSSH configure Portable, which was
generated by GNU Autoconf 2.59. Invocation command line was
$ ./configure --prefix=/home/scott --with-ssl-dir=/home/scott/src/openssl-0.9.7e
I would be happy to send the full config.log if it would help.
I had to set the LD_LIBRARY_PATH to include this directory as just
using --with-ssl-dir=[path_to_my_libcrypto] didn't work. Configure
would complain about the OpenSSL header not matching the library. I
hacked out the conftest.c that was failing in configure, added -H and
-v to CPPFLAGS and built it as a small app and ran ldd on it and it
reported that libcrypto was from /usr/lib. Hmm. The ld and gcc manual
pages sure seem to imply that if you pass -L and a path that that is
the path that is searched for libraries to link against. Sorry, I have
digressed.
I will look at this further.
Anyway, the main point/problem I am seeing is in make tests:
[scott at choke openssh-4.0p1]$ make tests
[trim]
run test agent.sh ...
ssh-add -l via agent fwd proto 1 failed (exit code 0)
/home/scott/src/openssh-4.0p1/ssh: error while loading shared
libraries: libcrypto.so.0.9.7: cannot open shared object file: No such
file or directory
agent fwd proto 1 failed (exit code 0)
ssh-add -l via agent fwd proto 2 failed (exit code 0)
/home/scott/src/openssh-4.0p1/ssh: error while loading shared
libraries: libcrypto.so.0.9.7: cannot open shared object file: No such
file or directory
agent fwd proto 2 failed (exit code 0)
failed simple agent test
make[1]: *** [t-exec] Error 1
make[1]: Leaving directory `/home/scott/src/openssh-4.0p1/regress'
make: *** [tests] Error 2
[scott at choke openssh-4.0p1]$
Here is some information from ldd:
[scott at choke openssh-4.0p1]$ ldd ./ssh-agent
libresolv.so.2 => /lib/libresolv.so.2 (0x009b5000)
libcrypto.so.0.9.7 =>
/home/scott/src/openssl-0.9.7e/libcrypto.so.0.9.7(0x00c71000)
libutil.so.1 => /lib/libutil.so.1 (0x00bcd000)
libz.so.1 => /usr/lib/libz.so.1 (0x003f2000)
libnsl.so.1 => /lib/libnsl.so.1 (0x06b46000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x06b77000)
libc.so.6 => /lib/tls/libc.so.6 (0x001c3000)
libdl.so.2 => /lib/libdl.so.2 (0x00313000)
/lib/ld-linux.so.2 (0x001aa000)
[scott at choke openssh-4.0p1]$ ldd ./ssh-add
libresolv.so.2 => /lib/libresolv.so.2 (0x009b5000)
libcrypto.so.0.9.7 =>
/home/scott/src/openssl-0.9.7e/libcrypto.so.0.9.7(0x00670000)
libutil.so.1 => /lib/libutil.so.1 (0x00bcd000)
libz.so.1 => /usr/lib/libz.so.1 (0x003f2000)
libnsl.so.1 => /lib/libnsl.so.1 (0x06b46000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x06b77000)
libc.so.6 => /lib/tls/libc.so.6 (0x001c3000)
libdl.so.2 => /lib/libdl.so.2 (0x00313000)
/lib/ld-linux.so.2 (0x001aa000)
[scott at choke openssh-4.0p1]$ ldd ./ssh
libresolv.so.2 => /lib/libresolv.so.2 (0x009b5000)
libcrypto.so.0.9.7 =>
/home/scott/src/openssl-0.9.7e/libcrypto.so.0.9.7(0x00de5000)
libutil.so.1 => /lib/libutil.so.1 (0x00bcd000)
libz.so.1 => /usr/lib/libz.so.1 (0x003f2000)
libnsl.so.1 => /lib/libnsl.so.1 (0x06b46000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x06b77000)
libc.so.6 => /lib/tls/libc.so.6 (0x001c3000)
libdl.so.2 => /lib/libdl.so.2 (0x00313000)
/lib/ld-linux.so.2 (0x001aa000)
[scott at choke openssh-4.0p1]$ ls -l
/home/scott/src/openssl-0.9.7e/libcrypto.so.0.9.7
-rwxrwxr-x 1 scott scott 1183316 May 17 09:41
/home/scott/src/openssl-0.9.7e/libcrypto.so.0.9.7
[scott at choke openssh-4.0p1]$ gcc --version
gcc (GCC) 3.4.3 20041212 (Red Hat 3.4.3-9.EL4)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I did a quick scan in bugzilla and didn't see anything. I searched the
mailing list archives and found this [1]. This test failure seems like
the same beast. Do I need to specify something else to configure?
cheers,
scott
[1] http://marc.theaimsgroup.com/?l=openssh-unix-dev&m=108246995620226&w=2
More information about the openssh-unix-dev
mailing list