From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Rottmann <a.rottmann@gmx.at>
Cc: guile-devel@gnu.org
Subject: Re: Build failure (stable-2.0, "make distcheck")
Date: Wed, 02 Jan 2013 18:08:25 +0100 [thread overview]
Message-ID: <87bod7bjhy.fsf@gnu.org> (raw)
In-Reply-To: <87k3rviy9b.fsf@delenn.home.rotty.xx.vu> (Andreas Rottmann's message of "Wed, 02 Jan 2013 13:07:44 +0100")
Andreas Rottmann <a.rottmann@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?
Ludo’.
next prev parent reply other threads:[~2013-01-02 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 17:34 Build failure (stable-2.0, "make distcheck") Andreas Rottmann
2013-01-02 11:35 ` Ludovic Courtès
2013-01-02 12:07 ` Andreas Rottmann
2013-01-02 17:08 ` Ludovic Courtès [this message]
2013-01-06 0:13 ` Andreas Rottmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bod7bjhy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=a.rottmann@gmx.at \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).