Hi,
Troy Benjegerdes wrote:
It looks like useing the '--with-krb5-conf=/usr/bin/krb5-config' option
creates a rather polluted KRB5LIBS list like this:
Adding -L/usr/lib -lkrb5 -lasn1 -lcrypto -lroken -lcrypt -lresolv to KRB5LIBS
It is not polluted, it should be used as it is by ld(1). Look
# /usr/heimdal/bin/krb5-config
usage: /usr/heimdal/bin/krb5-config [options] [libraries]
options: [--prefix[=dir]] [--exec-prefix[=dir]] [--libs] [--cflags]
libraries: krb5 gssapi kadm-client kadm-server
#
By default you get the 'krb5' output. The 'gssapi' adds one library extra.
When I use the following configure line, it works just fine:
KRB5CFLAGS=-I/usr/include/heimdal KRB5LIBS='-L/usr/lib-lkrb5 -lasn1
-lroken -lcrypt -lresolv' ./configure --with-krb5
I didn't try to see what other libs could be dropped as well.. Is this
something we should even bother with in AFS? Should it get reported to
the heimdal people?
I think thats why the krb5-config was introduced - to always show which libs
are to be used on the ld line and what is the path. So, it think you shouldn't
care. Only make sure that the krb5-config output reflects current state of the
machine - i.e. no update of openssl since you have installed heimdal
and that the openssl library is installed still in same place and similarly
for heimdal libs. Just use the other argument switches for krb5-config
and check the paths are valid. If they aren't, just reinstall heimdal
and you are done.
Martin
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
