>Perhaps a configure test to see if we find a system com_err and,
>if we find it, use it instead of the afs/com_err package?

Maybe we're going about this all wrong.  Perhaps we should just include
com_err.h instead of afs/com_err.h?  I suspect that afs/com_err.h is just
ancient cruft.

--Ken
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel

Reply via email to