openssh unix dev - Dec 2000 - Failure message of configure from openssh 2.3.0p1 is wrong.

Hi,

if i add --with-tcp-wrappers and --with-skey and don't have an
skey-library installed configure will fail with a message telling me
that I don't have libwrap installed. But after looking into config.log I
see the following:

|configure:6344: checking for libwrap
|configure:6356: gcc -o conftest -g -O2 -Wall -I. -I.   conftest.c -ldl -lnsl
-lz
|  -lutil -lpam -lcrypto  -lskey -lwrap 1>&5
|/usr/bin/ld: cannot find -lskey
|collect2: ld returned 1 exit status
|configure: failed program was:
|#line 6346 "configure"
|#include "confdefs.h"

|#include <tcpd.h>
|                                        int deny_severity = 0, allow_severity =
|0;
                                
|int main() {
|hosts_access(0);
|; return 0; }

So not libwrap is missing but instead the skey library. Please change
the configure error message to contain the right information. Thanks.

Ciao
     Christian
-- 
          Debian Developer and Quality Assurance Team Member
    1024/26CC7853 31E6 A8CA 68FC 284F 7D16  63EC A9E6 67FF 26CC 7853
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 242 bytes
Desc: not available
Url :
http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20001230/e23106b3/attachment.bin

On Sat, 30 Dec 2000, Christian Kurz wrote:
> Hi,
> 
> if i add --with-tcp-wrappers and --with-skey and don't have an
> skey-library installed configure will fail with a message telling me
> that I don't have libwrap installed. But after looking into config.log
I
> see the following:
> 
I get an error out if --with-skey fails to find the s/key libraries from
the current CVS tree when it checks for the s/key libraries.

2.3.0p1 was released on 11/06/2000.  I did an --with-skey update on
11/10/2000 which lets you define the path of the library in --with-skey
that also included a patch to make --with-skey work under the OpenSSH
portable (before this release it was broken).

*PLEASE* can we do us a favor and verify some of these problems with a
newer version?  A lot of what you've brought up has been fixed for almost
a month or more. =) Thanks.

I think we really do need a 2.4.0 release soon.=)

- Ben