In D51661#1181290, @ivy wrote:

i do not understand libgssapi enough to review this, but i am somewhat concerned about rick's comments: in upstream, is this library called libgssapi or libgssapi_krb5? if the latter, why do we need to rename it?

Cy reports that the gssd works when this patch plus mine
are applied. That is good news. Thanks Cy.

Now that we are not symlinking libgssapi.so to libgssapi_krb5.so removing libgssapi.so entirely, the ssh Makefiles required adjustment.

As of 73ed0c7992fd this patch is now required because /usr/src/lib/libgssapi (libgssapi.so) has no knowledge of MIT KRB5. Apps that wish to build against MIT KRB5 using its gssapi, i.e. gssd and ports, will fail.

In D51661#1181074, @rmacklem wrote:

Ok, I do not think the MIT library should be called libgssapi,
but in a different subdirectory.
be called, imho.
(libgssapi should only refer to the Heimdal one and should
never be referenced anywhere in the Makefiles unless it is
under ".if ${MK_MITKRB5} == "no".

i do not understand libgssapi enough to review this, but i am somewhat concerned about rick's comments: in upstream, is this library called libgssapi or libgssapi_krb5? if the latter, why do we need to rename it?

Ok, I do not think the MIT library should be called libgssapi,
but in a different subdirectory.
MIT calls it libgssapi_krb5 and that is what it should still
be called, imho.
(libgssapi should only refer to the Heimdal one and should
never be referenced anywhere in the Makefiles unless it is
under ".if ${MK_MITKRB5} == "no".

I am not conversant with the userspace builds/Makefile
stuff, so I have removed myself from the review.