problems compiling krb5.1.2 on solaris 8

[Marcus Watts]

Someone with the apparently bogus e-mail address Marc <syn_uw at NOSPAM_hotmail.com> writes:
> > making all in include/kerberosIV...
> > cd . && autoheader --localdir=../. 
> > sh: autoheader: not found
> 
> It looks like you need GNU autoconf...

autoconf is typically something a developer would run, after making
changes, before making a distribution.  Autoconf writes shell scripts
out that should, without further modification, customize a source
directory for building on a particular architecture.  Autoheader is
part of autoconf and writes out the config.h.in files used at
config-time to store machine dependencies for compile-time.  In any
event, you shouldn't need autoconf or its friends if you *just* intend
to build the software.

In this case, I'd say some makefile has a dependency rule that is
probably only really useful to the developer.  The dependency evidently
runs autoheader.  This is something that should not needed when just
building.  There's probably some file timestamp that's out of date that
causes the problem.  Installing some version of autoconf might fix or
at least bandaid this problem; but it might well bring on further nasty
problems because there are multiple slightly different versions of
autoconf, autoheader, libtools, and the like, and it's not always
possible to mix & match and get useful results.  Just for starters, the
MIT k5 release comes with its own copy of autoconf, which likely is not
the latest.

Uh, come to think of it, this *is* k5.  Well, there should be *a* copy
of autoheader in util/autoconf/autoheader.sh .  Whether that's the
*right* version to run is another question.  Probably the right fix is
to teach the k5 makefile not to run autoheader except on demand
(presumably by the developer).  An alternative less attractive fix
would be to fix the makefile such that it can find and run the
autoheader that is distributed with k5, rather than just assuming there
is a compatible version in the build-time environment.  Both of
these are things the mit k5 folks will have to address in their
next release.

To fix and build meanwhile; several fixes: touch config.h.in to
make sure it's more recent than whatever directory it lives in.
Or, install a copy of autoheader.sh somewhere where it can be
executed at run-time, as "autoheader".  After autoheader is
run, it may be necessary to blow away any .o's and run 'configure'
afresh, before another top level "make all" can be done.

			-Marcus Watts
			UM ITCS Umich Systems Group