Hi Ken! No worries, but thank you for your pointers so far! It is interesting that krb5-config --libs does indeed show k5crypto:
$ krb5-config --libs -L/opt/freeware/lib64 -Wl,-blibpath:/opt/freeware/lib64:/opt/freeware/lib:/usr/lib:/lib -L/opt/freeware/lib64 -L/opt/freeware/lib -Wl,-brtl -lpthreads -lkrb5 -lk5crypto -lcom_err It would appear that the output from that is not being used by OpenAFS though, because in the original error I also didn't see the -blibpath... arguments nor references to /opt/freeware/lib64. Thanks! -Ben ________________________________ From: Ken Hornstein <k...@cmf.nrl.navy.mil> Sent: Sunday, August 14, 2022 12:10 PM To: Ben Huntsman <b...@huntsmans.net> Cc: openafs-devel@openafs.org <openafs-devel@openafs.org> Subject: Re: [OpenAFS-devel] AIX build fails with missing symbol .krb5_c_make_random_key >Ah, yes, I believe you are right. That library does exist on my >system also, and I manually added it to Makefile.config and the build >continued. The question is then, why didn't ./configure detect it and >add it? I can't speak for that; I lack the energy at this time to go delving into the configure script for OpenAFS. The traditional way that Kerberos options are detected by autoconf (as Benjamin Kaduk alluded to) is you give it a path to a krb5-config script which will tell you the right compile and link-time options to build a Kerberos program. --Ken
