[3872] in Kerberos
Re: yet another k5b4 build fuckup
daemon@ATHENA.MIT.EDU (Paul Pomes)
Mon Sep 19 20:15:16 1994
To: kerberos@MIT.EDU
Date: 19 Sep 1994 22:36:46 GMT
From: p-pomes@mirage.cso.uiuc.edu (Paul Pomes)
Reply-To: P-Pomes@uiuc.edu
hobbit@elf.com (*Hobbit*) writes:
>Precisely what is the --with-krb4 configure option for? If the top-level
>configure is run with --with-krb4=something, kdc/Makefile expects to find
>libkrb.a and libkdc.a someplace, which don't exist where I'm building it.
>Does one need an existing installation of v4 to make that option worthwhile?
It establishes the base directory for locating v4 libraries. It should
also locate the v4 include files as compiling with one and linking with
the other is an excellent way to crash. You do need to have built v4
first. My installation placed libkrb.a, libdes.a, and libkdc.a under
/usr/local/lib while the include files went into
/usr/local/include/kerberosIV. I then moved the v5 src/include/kerberosIV
directory to src/include/kerberosIV- and make src/include/kerberosIV a
symlink to /usr/local/include/kerberosIV .
configure was then handed --with-krb4=/usr/local .
You'll still need to edit the Makefiles under src/appl/telnet to
add -DDES -DKRB4 (libtelnet/Makefile will need -DDES_ENCRYPTION as well)
plus -L/usr/local/lib -lkrb -ldes to the LIBS entry.
Does anyone have a working configuration for telnetd under Solaris? I've
played with using login.bsd and the existing /bin/login program w.o. good
effect. My next step will be to load the Solaris source CD-ROM and add
the -f flag locally. I really don't want to do this as it makes our
drop-in package fragile (any patch could overwrite our changes).
/pbp
--
The social circumstances appropriate for grenades just don't occur that often.
-- Paul Pomes
For shame, Paul. Congress meets daily. -- Steve Dorner
