What's weird is that those symbols are all defined in
$ nm /usr/lib/libgssapi_krb5.dylib | egrep '_gss_mech_krb5|_decode_krb5_ticket|_krb5_init_ets|_krb5_write_message'
94473284 t _decode_krb5_ticket
a43d4ee4 s _gss_mech_krb5
a43d4ee8 s _gss_mech_krb5_old
9448e6f8 t _krb5_init_ets
9446ff90 t _krb5_write_message
I'm new to Mac OS X, so I suspect I'm missing something about the way
linking works in this environment. I also made the possibly-naive
assumption that I could link to the Mac OS X Kerberos libraries the
same way I would build with the MIT libraries, as the OS X Kerberos seems
to be a port of MIT.
Ed Ravin | "The law, in its majestic equality, forbids the rich as
| well as the poor to sleep under bridges, to beg in the
eravin@ | streets, and to steal bread."
panix.com | --Anatole France, Le Lys Rouge 
Kerberos mailing list [hidden email] https://mailman.mit.edu/mailman/listinfo/kerberos
> I'm new to Mac OS X, so I suspect I'm missing something about the way
> linking works in this environment. I also made the possibly-naive
> assumption that I could link to the Mac OS X Kerberos libraries the
> same way I would build with the MIT libraries, as the OS X Kerberos seems
> to be a port of MIT.
C-Kermit does not build for MacOSX with Kerberos because it relies on
some interfaces and symbols which are considered private and are not
exported by the libraries.
I have placed an untested binary built on MacOS X at