"dan" = Dan Harkless <[EMAIL PROTECTED]> (me)
"danw" = Dan Winship <[EMAIL PROTECTED]>
"simonb" = Simon Burge <[EMAIL PROTECTED]>
dan: Okay, I installed ssh-1.2.27 and was able to successfully check out the
dan: nmh development tree with CVS.
dan:
dan: I successfully configured (one oddment here -- by default the
dan: installation prefix came out as /usr/local/nmh -- didn't it used to be
dan: /usr/local?)
I've now checked the ChangeLog and I see that I was wrong -- Richard changed
the installation prefix to /usr/local/nmh way back in December 1996.
Not sure if it was /usr/local or /usr/local/mh before this, but I'd rather
see it be /usr/local. This would be more in line with the majority of free
source packages out there. I don't believe there are any name conflicts
between nmh and other common packages out there (other than MH, which we're
supposed to be replacing anyway), so it seems like this should be fine.
People who want a nonstandard installation directory like /usr/local/nmh or
/usr/local/stow/nmh-1.0.1 can always do that in the usual way, with
configure --prefix=* or make prefix=*.
On the other side of the coin, the only reason I can see for leaving it
/usr/local/nmh is that it's been that way for some time.
Anyone have any objections to changing the default?
dan: and tried a 'make', but it failed right at the beginning with:
dan:
dan: cd . && autoheader
dan: /bin/sh: autoheader: not found.
dan: make: *** [stamp-h.in] Error 127
dan:
dan: What the heck is 'autoheader'?? Never heard of it. I did a grep
dan: through all the nmh files, and the only mentions of it are the call in
dan: Makefile[.in] and a note that config.h[.in] was automatically generated
dan: with it.
dan:
dan: If this is a new required tool, shouldn't it be mentioned in one or
dan: more of the documentation files? Is it only required for developers,
dan: or for people building from the stable tarballs as well? Is it part of
dan: GNU autoconf? If not, where does one get it?
simonb: Autoheader is used to rebuilt config.h.in from configure.in after
simonb: that changes. Only people to modify configure.in need autoheader -
simonb: usually developers, and not builders.
danw: It's not needed by end users, but you do need it if you're building
danw: from the CVS repository.
To clarify the contradiction here, Dan W. is correct -- it's necessary to
build from the CVS repository, even if you don't change configure.in.
danw: I guess that should be documented somewhere. (As well as the fact
danw: that if you change configure.in you'll need autoconf.)
Is it possible the Makefile, timestamps, or CVS repository could be tweaked
so that autoheader is run only if you change configure.in?
simonb: It is part of autoconf.
danw: It's not part of autoconf, but you get it from your friendly local
danw: ftp.gnu.org mirror.
This time Simon is correct -- autoheader is part of autoconf (available,
as Dan W. says, from ftp.gnu.org).
When a note is added about the autoheader requirement, it'd be nice to also
mention that GNU m4 needs to be installed and working before attempting to
configure autoconf.
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please do not post this
[EMAIL PROTECTED] | private email address to the USENET or WWW. Thank you.
