Lars Hecking <[EMAIL PROTECTED]> writes:
> Michael Tatge writes:
> > Lloyd Zusman muttered:
> > > I have recently downloaded the current unstable mutt release, version
> > > 1.3.14. It doesn't come with a `configure' script
> >
> > Mine does:
>
> Maybe he downloaded the cvs version? It does indeed not have a configure
> script, and one needs to run the included prepare script to generate all
> auto* files.
Aha! Yes, I ran the `prepare' script, and indeed it worked fine.
Thank you very much.
> If the generated configure script is broken, someone may have messed
> with autoconf on that box.
My `autoconf' is fine. But given what is done within the `prepare'
script, it's clear that simply running `autoconf' alone isn't enough.
The sequence that the `prepare' script performs is ...
aclocal -I m4
autoheader
cd m4
make -f Makefile.am.in
automake -i
autoconf
... etc. ...
>From this, it's clear that the first 5 steps have to run prior to
`autoconf', in order for `autoconf' to work properly. This is what I
was trying to find out in my initial message. But using `prepare' is
even better.
The `prepare' script is mentioned within the `INSTALL' file. However,
I didn't initially run it, because this documentation states that
`prepare' is used with a CVS retrieval, and I didn't get this source
from CVS, but rather, I downloaded the following tarball:
"mutt-unstable-20010211.tar.gz".
Now I realize that this tarball probably contains the same data as
what I would have gotten if I went directly to CVS, and therefore, I
now see that the `prepare' script applies to this tarball, as well.
Thanks again.
--
Lloyd Zusman
[EMAIL PROTECTED]
