>> BTW, are you planning on requiring libkopenafs to link against com_err? > >No, it shouldn't need to link with anything Kerberos-related, at least for >the first round. The goal is to implement only k_hasafs, k_pioctl, >k_unlog, and k_setpag.
My concern was not having to link against a Kerberos-related library; my real concern was having to link against an AFS library. One of the giant problems I have with aklog is the fact that there are two com_err libraries (the AFS one and the Kerberos one), and you have to do all these gyrations since you can't link against both. That's why a lot of the time you only get AFS error messages or Kerberos error messages; rarely do you get both in a single aklog. If libkopenafs didn't require the AFS com_err library, that would be a huge win. >If you need the other stuff (anything starting with krb_* for instance), >that isn't in the original plan. I don't know if the above would be >enough. No, the functions I'm concerned about all begin with pr_. --Ken _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
