Coy Hile wrote:
On Mon, 19 Sep 2005, Douglas E. Engert wrote:o The configure was done using: KRB5CFLAGS="-I$K5BUILD/$SYS/krb5/include" KRB5LIBS="/usr/lib/gss/mech_krb5.so -R/usr/lib/gss" export KRB5CFLAGS export KRB5LIBS ./configure --enable-transarc-paths \ --with-krb5=yes \ --enable-largefile-fileserver \ --host=sparc-sun-solaris2.10
The rest of the note sent you talked about getting the opensolaris version of krb5.h, and the risks you take in doing this. (See Jeff's note) (bug the Sun people to distribute these headers.) Also as said, I was using gssklog, that uses a standrd API that does not have these problems. I build from AFS, and $K5BUILD point into our cell where these where at. $SYS is in effect @sys i.e. sysname of sun4x_510
Okay Doug, I have another question. You reference $K5BUILD and $SYS in the environment variables above. From that, I gather that you're populating the filesystem with various krb5 headers that (for reasons unknown to us) Sun do not ship. Where in the filesystem do you put those headers? Thanks again, and I apoplogize for seeming like such a neophyte; Kerberized services are something of a new thing for me. -- Coy Hile [EMAIL PROTECTED]
-- Douglas E. Engert <[EMAIL PROTECTED]> Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444 _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
