lilypond-devel
[Top][All Lists]
Advanced

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

Re: web build failure in docs/fr/user/


From: John Mandereau
Subject: Re: web build failure in docs/fr/user/
Date: Mon, 18 Feb 2008 20:49:39 +0100

Le dimanche 17 février 2008 à 17:30 -0800, Graham Percival a écrit :
> Web build failure in Documentation/fr/user/
> 
> Reading lilypond-learning.tely...
> Dissecting...
> Writing snippets...Traceback (most recent call last):
>   File "/home/lilypond/lilypond/scripts/lilypond-book.py", line 1883,
> in ? main ()
>   File "/home/lilypond/lilypond/scripts/lilypond-book.py", line 1849,
> in main chunks = do_file (file)
>   File "/home/lilypond/lilypond/scripts/lilypond-book.py", line 1741,
> in do_file do_process_cmd (chunks, input_fullname)
>   File "/home/lilypond/lilypond/scripts/lilypond-book.py", line 1613,
> in do_process_cmd map (Lilypond_snippet.write_ly, ly_outdated)
>   File "/home/lilypond/lilypond/scripts/lilypond-book.py", line 1096,
> in write_ly outf = open (self.basename () + '.ly', 'w')
> IOError: [Errno 40] Too many levels of symbolic links:
> 'lily-354d7a5697.ly' make[1]: *** [out-www/lilypond-learning.texi]
> Error 1 make[1]: Leaving directory
> `/home/lilypond/lilypond/Documentation/fr/user' make: *** [web] Error 2
> address@hidden:~/lilypond/Documentation/fr/user$

This bug is certainly caused by symlinks in
Documentation/<LANGS>/user/out-www, which are left over from the old
build system.  There shouldn't be lily-* symlinks any more there.  I
don't know actually, because I made web-clean in
Documentation/<LANGS>/user/ (and only there) before testing the new
build system for the first time.


> After cleaning out the previous `make web' and starting frmo scratch,
> I get this:
> 
> args /usr/bin/python ../../../buildscripts/html-gettext.py 
> ../../../buildscripts /home/lilypond/lilypond/Documentation/po/./out-www
> fr find ./out-www -name '*.html' | xargs grep -L --label=""
> 'UNTRANSLATED NODE: IGNORE ME' | sed 's!./out-www/!!g' |
> xargs /usr/bin/python ../../../buildscripts/mass-link.py
> --prepend-suffix .fr
> hard ./out-www /home/lilypond/lilypond/Documentation/user/./out-www
> lilypond-learning.pdf lilypond-program.pdf lilypond.pdf mass-link.py
> find ./out-www \( -name 'lily-??????????.png' -o -name
> 'lily-??????????.ly' \) | sed 's!./out-www/!!g' |
> xargs /usr/bin/python ../../../buildscripts/mass-link.py
> hard ./out-www /home/lilypond/lilypond/Documentation/user/./out-www
> mass-link.py Traceback (most recent call last): File
> "../../../buildscripts/mass-link.py", line 64, in ? map (force_link,
> sourcefiles, destfiles) File "../../../buildscripts/mass-link.py", line
> 62, in force_link link (src, dest) OSError: [Errno 17] File exists make
> [1]: *** [local-WWW] Error 123 rm out-www/lilypond-program.pdftexi
> out-www/lilypond.pdftexi out-www/lilypond-program.texi
> out-www/lilypond.texi out-www/lilypond-learning.pdftexi
> out-www/lilypond-learning.texi make[1]: Leaving directory
> `/home/lilypond/lilypond/Documentation/fr/user' make: *** [web] Error 2
> address@hidden:~/lilypond/Documentation/fr/user$ 

I can't reproduce this, so I guess you make web with EXTERNAL_BINARY,
which results in using an old lilypond-book, incompatible with the new
build system -- what actually happens is that old lilypond-book don't
find snippets in directories paased through -I command line option
(namely Documentation/user/out-www), so it rebuilds all ly snippets,
then mass-link.py tries to link lily-*.png's that already exist in
Documentation/user/out-www, which causes this failure.

Try the following trick: make a copy of latest master lilypond-book.py,
replace

"""
@relocate-preamble@
"""

with the preamble from your installation's lilypond-book, and overwrite
the latter with the new version you made by hand.

When building docs with EXTERNAL_BINARY, you're at the mercy of such
problems, but you know this :-), and fortunately the makefiles don't
change too frequently.

Anyway, I'll try to make mass-link.py more robust so it doesn't try to
link existing files.

Thanks for the report,
John






reply via email to

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