[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Build failure (stable-2.0, "make distcheck")

From: Andreas Rottmann
Subject: Re: Build failure (stable-2.0, "make distcheck")
Date: Sun, 06 Jan 2013 01:13:42 +0100

address@hidden (Ludovic Courtès) writes:

> Andreas Rottmann <address@hidden> skribis:
>> It is the case; is present, but it seems that it's not newer
>> that one of the sources it's built from:
>> % tar --utc -tvf _build/guile- | grep -E 
>> '\.(info|texi)$' | awk '{ print $4 " " $5 " " $6 }' | sort | tail -n2
>> 2012-12-26 13:59 guile-
>> 2012-12-26 13:59 guile-
>> Probably standard-library.texi is created just a tiny bit earlier than
>> (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 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

|    Prerequisite `effective-version.texi' is newer than target 
|   Must remake target `../../../doc/ref/'.
| make[5]: Entering directory 
| [... actual failure happens here ... ]

While "doc/ref/effective-version.texi", as contained in the tarball, is
indeed older than (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 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-


% ls --full-time doc/ref/ doc/ref/effective-version.texi              
-r--r--r-- 1 rotty rotty    27 2012-12-26 17:35:08.000000000 +0100 
-r--r--r-- 1 rotty rotty 29821 2012-12-26 17:35:16.000000000 +0100 


% ls --full-time _build/doc/ref/effective-version.texi            
-rw-r--r-- 1 rotty rotty 27 2013-01-05 16:32:37.150982801 +0100 


| ...
| 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 -- <>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]