[18997] in Kerberos_V5_Development
Re: [patch] krb5 HEAD fails to build on RHEL5/Linux/IA64 with $
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Sep 2 12:34:36 2014
Message-ID: <5405ED86.6040307@mit.edu>
Date: Tue, 02 Sep 2014 12:17:10 -0400
From: Greg Hudson <ghudson@mit.edu>
MIME-Version: 1.0
To: Roland Mainz <rmainz@redhat.com>, krbdev@mit.edu
In-Reply-To: <1665048908.27071216.1409597832877.JavaMail.zimbra@redhat.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On 09/01/2014 02:57 PM, Roland Mainz wrote:
> -VERTO_LIBS="-lverto"
> +VERTO_LIBS="-lverto -lm"
This is too broad. libm should not be a linker dependency of krb5kdc
and kadmind for non-static builds or when the system libverto is used.
Taking a step back, I think we are likely to get rid of static linking
support rather than add more complexity to fix or improve it.
Support for static linking was removed in 1.7 because our architecture
was moving increasingly in the direction of loading plugin modules,
including some in-tree modules like PKINIT, KDB modules, and now the TLS
plugin module. I added limited static linking support back in for 1.8
in order to be able to do test coverage analysis with gcov, but gcov now
works with shared libraries, so the motivation is gone. In the
meantime, we have added another pluggable interface with an in-tree
module, and have expanded our automated test coverage to include PKINIT
and the new TLS plugin module, neither of which will work in a static build.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
