Hi Eric, thanks for taking the time to file this bug report.
I've confirmed that this bug exists all the way back to lucid. In fact it also affects CentOS/RHEL 6. I cannot seem to get krb5_cccol_lock or unlock to link.
I'm not sure its a bug though. The function is not exported, so it shouldn't actually appear in an upstream build of the library.
Its not clear to me that the packaging is doing anything "strange" to build and link the libraries. I suspect this may be something that upstream does differently depending on how you build it. It would be helpful in figuring out how this can be fixed if you provided the exact steps you used to produce libraries with these symbols from upstream source.
For now I'm going to mark the bug as Confirmed, with an importance of Medium. Please provide that feedback so we can work on pushing the bug upstream if necessary.
Hi Eric, thanks for taking the time to file this bug report.
I've confirmed that this bug exists all the way back to lucid. In fact it also affects CentOS/RHEL 6. I cannot seem to get krb5_cccol_lock or unlock to link.
I'm not sure its a bug though. The function is not exported, so it shouldn't actually appear in an upstream build of the library.
./src/lib/ krb5/libkrb5. exports: krb5_cccol_ cursor_ free krb5/libkrb5. exports: krb5_cccol_ cursor_ new krb5/libkrb5. exports: krb5_cccol_ cursor_ next
./src/lib/
./src/lib/
Those 3 are, but these two are not listed.
Its not clear to me that the packaging is doing anything "strange" to build and link the libraries. I suspect this may be something that upstream does differently depending on how you build it. It would be helpful in figuring out how this can be fixed if you provided the exact steps you used to produce libraries with these symbols from upstream source.
For now I'm going to mark the bug as Confirmed, with an importance of Medium. Please provide that feedback so we can work on pushing the bug upstream if necessary.