Ok, I finally figured out what's wrong ...
Since I don't have root, I need to specify a different lockdir location,
like my $HOME/locks.
To do that, I edited config.h and acconfig.h.
That triggered Make to want to run 'autoheader'.
So I commented out the tags that it wants to run and it compiles.
And now 'inc' works.
But had I let it ran autoheader, would it wipe out my changes in the *.h files?
Here's a summary of what I learnt in setting this up:
1. I DON'T need to add the line #undef as suggested in the MACHINES file
for HP-UX 10.20.
In fact, adding the line causes 'scan' to coredump.
2. To change file locking defaults, you have to change the *.h files.
3. You may want to have autoconf handy.
So now 'inc' is working, I'm looking around for an external MIME viewer. Any
suggestions?
Last but not least, thanks to Dan Harkless, Emile Carcamo and others who helped me and
responed to my posting.
Thanks again.
> ----------
> From: Dan Harkless[SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, January 26, 2000 4:38 PM
> To: EXT-Li, Yung A
> Cc: 'nmh mailing list'
> Subject: Re: Help: 'inc' won't work
>
>
> "EXT-Li, Yung A" <[EMAIL PROTECTED]> writes:
> > > > But I've even wipe out the source tree and re-extracted the tar
> > > > files. Same problem.
> > >
> > > Which same problem? It still wants to run autoheader? That shouldn't be
> > > the case -- the timestamps are set up correctly. You can use make -d to
> >
> > Yes, it still wants to run autoheader. That's why I'm pulling my hair out ...
> > I'll include the error mesg from 'make'.
>
> Well, not really an error message, but a debug message. If you run with -d,
> then just before it tries to run autoheader, there should be an explanation
> of which dependency it thinks is out-of-date. You can then examine the
> timestamps of the files involved and 'touch' as necessary.
>
> Still don't see why you'd have to do this, though, if you're using the original
> nmh-1.0.2.tar.gz from mhost.com. (I could see it if you were using CVS
> source or were using a .tar file you had re-created after doing local
> configuration.)
>
> > Like I said, this thing did build the first time I try it. did not have
> > this 'autoheader' problem before... I don't think my make is broken,
> > unless someone changed it between Monday night and last night.
>
> You could always check the timestamp on it. You might also see which make
> your path is pointing to (e.g. GNU make in /usr/local/bin or vendor make in
> /usr/bin).
>
> And as I said previously, installation of GNU autoconf
> (<ftp://ftp.gnu.org/autoconf/>) isn't difficult and will also solve your
> build problem.
>
> -----------------------------------------------------------------------
> Dan Harkless | To prevent SPAM contamination, please
> [EMAIL PROTECTED] | do not post this private email address
> SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
>
