According to [EMAIL PROTECTED]:
> Gilles Detillieux writes:
> >
> > OK, but then why was make running automake on my system? Was it
> > because the mod. times got messed up after I applied Loic's patch?
>
> Yes exactly. I forgot that in my previous mail but the effect is
> the same as with a checkout.
The same problem could occur if someone copies the files from one place to
another and forgets the -p option, or untars the archive on one system and
FTPs it over to another.
> > If so, this could also pose a problem when, for instance, someone grabs
>
> It is a problem because people must have automake/libtool/autoconf updated
> to the right version. It is not a problem precisely because makefiles now
> contain dependencies that will regenerate all needed files when one is
> modified.
> I hope you'll find this acceptable and I'm sorry I didn't think to include
> a warning about this problem.
Personally, I'd prefer to see the automake/autoconf stuff handled the way
autoconf was handled before - you had to specify a make target explicitly
to regenerate the ./configure script. A "make" or "make all" wouldn't
accidentally trip these rules, so regardless of how you obtained your
source tree, you could still recompile it on a system without autoconf
or automake, or with the wrong versions of these tools.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] containing the single word "unsubscribe" in
the SUBJECT of the message.
