Re: Build environment incomplete and how to handle that.

[Dave Love <d.love@dl.ac.uk>]

[Apologies if this is a repeat.  It seems to have got a spurious
bounce the first time.]

Harald Barth <haba@pdc.kth.se> writes:

> I compiled heimdal on a box that was not installed with all the devel
> tools. I run configure and then make and got the following error:
>
> gcc -Wall -Wmissing-prototypes -Wpointer-arith -Wbad-function-cast -Wmissing-declarations -Wnested-externs -g -O2 -o testit testit.o  ./.libs/libeditline.a ../../lib/vers/.libs/libvers.a ../../lib/roken/.libs/libroken.a -lcrypt -lresolv
> ./.libs/libeditline.a(editline.o): In function `TTYinfo':
> clear_line/editline.c:245: undefined reference to `tgetent'
> clear_line/editline.c:250: undefined reference to `tgetstr'
> clear_line/editline.c:255: undefined reference to `tgetnum'
> clear_line/editline.c:256: undefined reference to `tgetnum'
> collect2: ld returned 1 exit status
>
> So, what is wrong? Couldn't configue have told me that it's no idea in
> starting make without curses (I needed ncurses-devel).

Either that or conditionally build the things which need it.  (Why is
a homemade `AC_FIND_FUNC_NO_LIBS' used rather than `AC_SEARCH_LIBS'?
It should at least not have an `AC_' prefix, I think.)

> The same goes for lex and yacc.

They shouldn't be necessary for non-development use.  The generated
files should be shipped with the sources.  (That's according to the
GNU conventions, which seem sensible.)  I thought Automake did it that
way automagically, though.  Is it just that the tarball isn't made
properly?