l...@gnu.org (Ludovic Courtès) writes:
> Andreas Rottmann <a.rottm...@gmx.at> skribis:
>
>> It is the case; guile.info is present, but it seems that it's not newer
>> that one of the sources it's built from:
>>
>> % tar --utc -tvf _build/guile-2.0.7.13-b5d83.tar.gz | grep -E
>> '\.(info|texi)$' | awk '{ print $4 " " $5 " " $6 }' | sort | tail -n2
>> 2012-12-26 13:59 guile-2.0.7.13-b5d83/doc/ref/guile.info
>> 2012-12-26 13:59 guile-2.0.7.13-b5d83/doc/ref/standard-library.texi
>>
>> Probably standard-library.texi is created just a tiny bit earlier than
>> guile.info (in the same second). That might be the reason the build
>> tries to run makeinfo inside the unpacked "dist" tarball?
>
> Can you unpack the tarball and check that hypothesis?
>
It turned out my hypothesis was wrong, the guile.info actually has a
newer timestamp. I've now run a build using "make distcheck --debug=v"
and attached the log for future reference. It seems that problem is the
following:
,----
| Prerequisite `effective-version.texi' is newer than target
`../../../doc/ref/guile.info'.
| Must remake target `../../../doc/ref/guile.info'.
| make[5]: Entering directory
`/home/rotty/src/guile/_build/guile-2.0.7.12-c23fb/_build/doc/ref'
| [... actual failure happens here ... ]
`----
While "doc/ref/effective-version.texi", as contained in the tarball, is
indeed older than guile.info (A), it seems a build-directory version of
"effective-version.texi" is generated by configure (B, C), and that copy
is then used by make for calculating whether guile.info needs to be
(re-)built, as indicated by the above log snippet.
The below commands are executed inside the extracted copy of the
tarball, in which the build fails
(i.e. /home/rotty/src/guile/_build/guile-2.0.7.12-c23fb/):
(A)
% ls --full-time doc/ref/guile.info doc/ref/effective-version.texi
-r--r--r-- 1 rotty rotty 27 2012-12-26 17:35:08.000000000 +0100
doc/ref/effective-version.texi
-r--r--r-- 1 rotty rotty 29821 2012-12-26 17:35:16.000000000 +0100
doc/ref/guile.info
(B)
% ls --full-time _build/doc/ref/effective-version.texi
-rw-r--r-- 1 rotty rotty 27 2013-01-05 16:32:37.150982801 +0100
_build/doc/ref/effective-version.texi
(C)
,----
| ...
| config.status: creating doc/ref/effective-version.texi
| ...
`----
At least that's what I read out of the logs. I just wonder why nobody
else seems to have run into this issue, which now looks like a genuine
buildsystem bug to me. Thoughts?
Kind Regards, Rotty
--
Andreas Rottmann -- <http://rotty.xx.vu/>
