Adding automake to the list, as with the information below this is now
looking like an automake issue.
I rolled another release and here's what I see:
harlan@hms-mbp11% ls -ltrT config.h.in sntp/config.h.in aclocal.m4
sntp/aclocal.m4 sntp/m4/version.m4
-rw-rw-r-- 1 harlan wheel 40 Feb 23
On 02/27/2014 04:47 AM, Harlan Stenn wrote:
So while the filestamps are technically correct, the generated Makefile
*will* see that version.m4 is newer than config.h.in and regenerate it
via Makefile dependencies.
I suspect the answer is that at the end of the bootstrap script, if the
Hi Peter,
Peter Johansson writes:
On 02/27/2014 04:47 AM, Harlan Stenn wrote:
So while the filestamps are technically correct, the generated
Makefile *will* see that version.m4 is newer than config.h.in and
regenerate it via Makefile dependencies.
I suspect the answer is that at the end of
On 02/27/2014 11:05 AM, Harlan Stenn wrote:
Yes, understood. And the problem is that am__configure_deps includes
am__aclocal_m4_deps, which includes aclocal.m4.
Inaccurate. am__configure_deps includes aclocal,m4 via variable
$(ACLOCAL_M4). am__aclocal_m4_deps describes which files
Peter Johansson writes:
On 02/27/2014 11:05 AM, Harlan Stenn wrote:
Yes, understood. And the problem is that am__configure_deps includes
am__aclocal_m4_deps, which includes aclocal.m4.
Inaccurate. am__configure_deps includes aclocal,m4 via variable
$(ACLOCAL_M4). am__aclocal_m4_deps
