Simon Peyton-Jones wrote:
> To be fair the 'how to build' notes do say "run autoconf first".
> I don't think autoheader is necessary. (If it is, someone say so,
> in which case it should get added to the build notes.)
It *was* necessary to run autoheader after I've changed acconfig.h
to re-generate mk/config.h.in.
> It's hard to specify exactly when its necessary to re-run autoconf.
>
> Specific suggestions for better documentation always welcome.
> If they take the form of draft text that's even better.
My suggestion is simple:
* "Normal" (= sane :-) people don't need autoconf/autoheader,
because configure, mk/config.h.in, ... should always match
their counterparts configure.in, acconfig.h.in, ... in a
source distribution.
* People compiling from CVS should always run both
autoconf/autoheader in fptools and fptools/ghc. It doesn't
hurt if nothing changed and guarantees consistency.
Cheers,
Sven
--
Sven Panne Tel.: +49/89/2178-2235
LMU, Institut fuer Informatik FAX : +49/89/2178-2211
LFE Programmier- und Modellierungssprachen Oettingenstr. 67
mailto:[EMAIL PROTECTED] D-80538 Muenchen
http://www.informatik.uni-muenchen.de/~Sven.Panne
