Keresztfalvi Gabor <[EMAIL PROTECTED]> writes:
> On 3 Oct 1999, Niels M�ller wrote:
>
> Hmmm. I don't want to mess my machine with new packages, till I install a
> current linux distro... Maybe in november...
Autoconf is really easy. It's just a bunch of m4 scripts. ./configure
&& make install probably takes less than a minute, as it doesn't need
to compile anything.
Personally, I usually let the programs that came with the system live
in /usr/bin, /usr/lib, etc, untouched, and whenever I need something
else or a newer version I usually compile it from source and install it
in /usr/local rather than messing with the packaging systems. Ok, this
approach won't work for core packages like libc, but autoconf is not
one of those.
> > config.h.in is generated automatically from configure.in and
> > acconfig.h, and this rule says how and when to do that. If it is
> > invoked, it is probably because either (i) you have edited
> > configure.in or acconfig.h, or (ii) for some reason stamp-h.in doesn't
> > exist or has the wrong timestamp.
> (i) nope, I didn't change configure.in/acconfig.h
> (ii) stamp-h.in exists, and has the same timestamp as in the tarrball (Oct 2
> 00:59).
Strange. What are the timestamps on the other involved files
(configure.in, acconfig.h and aclocal.m4)?
The make rule looks ok to me. And I didn't even write it myself, it's
generated by automake, so I would guess that it is fairly standard.
Let me know if you find out exactly what went wrong; if not you can
probably work around it by touching stamp-h.in or something like that.
/Niels
