lilypond-devel
[Top][All Lists]
Advanced

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

Re: Failed 'make' with 2.17.27 from tarball


From: James
Subject: Re: Failed 'make' with 2.17.27 from tarball
Date: Mon, 30 Sep 2013 11:07:07 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0

On 30/09/13 08:28, David Kastrup wrote:
Thomas Morley <address@hidden> writes:

Hi,

for some testings I tried to compile 2.17.27 from the tarball to be found at:
http://lilypond.org/website/development.html
on Ubuntu 10.04 64-bit

Without success. The terminal-output points me to
contributor.makeinfo.log

This file contains:
"
/home/me/lilypondH/lilypond-2.17.27/Documentation/contributor/programming-work.itexi:69:
warning: @image file `lilypond/pictures/architecture-diagram.txt' (for
text) unreadable: No such file or directory.
That one's harmless (for the sake of image-less info format, makeinfo
looks for ASCII art).

out/contributor.texi:101: @verbatiminclude `ly-grammar.txt': No such
file or directory.
makeinfo: Removing output file `out/lilypond-contributor.info' due to
errors; use --force to preserve.
That one isn't.

Do we have a problem?
Looks like it.  There were several recent changes in the build system,
actually even a change that was supposed to actually distribute
ly-grammar.txt.  It's conceivable that Make sees the distributed
ly-grammar.txt and does not bother regenerating it, while makeinfo
doesn't find it.  Which would mean that distributing ly-grammar.txt is
what causing the problem.  It may also be that unrelated problems are
involved.

Did you try building in-place or in a separate build directory?


Is it safe to assume the tarball contains everything that would be in a normal 'git' repository?

I am never sure if test-patchy is really giving those makefile changes that Julien submits a 'run for their money' during the testing phase, however if simply doing a manual make/make doc in $LILYPOND_GIT would prove that then I can easily check this.

James




reply via email to

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