Content-Type: text/plain; charset=UTF-8
Content-Length: 1162

On Sat, May 10, 2014 at 9:54 PM, Richard Basch via RT <
rt-comment@krbdev.mit.edu> wrote:

> If you use CC="gcc -m64 -static -static-libgcc" (the -static-libgcc is
> optional) and specify -without-system-verto during configure, the build
> will fail in kdc:
> ../lib/libverto.a(verto-k5ev.o): In function `periodic_recalc':
> verto-k5ev.c:(.text+0x2f0f): undefined reference to `ceil'
>
> Unfortunately, -lverto is the last entry present on the link line, and the
> configure steps don't appear to readily allow you to specify extra libs to
> be included at the end, such as -lm.


That's funny, I've just noticed that today and I was about to ask the ml :o

I'm actually using --enable-static --disable-shared , and I've noticed
there is logic in configure (aclocal.m4 really) to tweak a few variables if
enable_static. There might be an "ok" fix there.
However in a pinch I just added -lm to VERTO_LIBS in configure/configure.in;
that got me though the build at least.



BTW this is not the only problem I've seen when doing a static build:
* iaesx64.s fails to build because the only Makefile rule is to build a .so
* building with -pie causes link failures