Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Status: Accepted Owner: Labels: Type-Defect Priority-Critical New issue 1633 by percival.music.ca: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 We can't compile git master any more; some files in Documentation/web/ly-examples/ segfault when compiled as part of "make doc" (although not when compiled on their own) git bisect identified this commit: dffe04e8e1a7c0b94fdfc30e44fe141dfbe7cbec This does not affect stable/2.14 (since that commit isn't backported), but not being able to compile the docs with git master is critical because it causes some inconvenience to documentation writers. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Comment #1 on issue 1633 by reinhold...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 I can't reproduce this on an Ubuntu Linux 32-bit machine. A clean doc build goes through without any problems... ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Comment #2 on issue 1633 by reinhold...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 To be able to debug this problem, can someone who can reproduce this problem send me the .ps file that fails to convert to .pdf? In particular, the problem might be scm_from_locale_stringn, which I'm using to convert the char[...] array in C to a SCM object. In the .ps file I can see what is actually written (should be either latin1 or utf-16be, but apparently on some platforms this fails...) Thanks, Reinhold ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Am Sonntag, 24. April 2011, um 04:06:08 schrieb Colin Campbell: > Here you go, Reinhold. I've done a complete new clone, then git pull > -r, ./autogen.sh --noconfigure, mkdir build, cd build , make then make > doc. The doc build failed identically to my original report, and I've > attached the bach-schenker.ps file. Hmm, that .ps file does not even contain a DOCINFO block. However, it seems to be truncated, so lilypond fails earlier than I suspected... Are you on a 32 or a 64 bit system? And which OS? Thanks, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Comment #3 on issue 1633 by colinpkc...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 For tidiness, I'm attaching the file Reinhold asked for, and quoting his reply: Am Sonntag, 24. April 2011, um 04:06:08 schrieb Colin Campbell: > Here you go, Reinhold. I've done a complete new clone, then git pull > -r, ./autogen.sh --noconfigure, mkdir build, cd build , make then make > doc. The doc build failed identically to my original report, and I've > attached the bach-schenker.ps file. Hmm, that .ps file does not even contain a DOCINFO block. However, it seems to be truncated, so lilypond fails earlier than I suspected... Me: I'm running Ubuntu 10.10 on a 64-bit dual core machine, Reinhold. I won't make any changes to /lilypond-git in case you need other parts of the system in the same state. Are you on a 32 or a 64 bit system? And which OS? Thanks, Reinhold Attachments: bach-schenker.ps 286 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Comment #4 on issue 1633 by percival.music.ca: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 Here's two bach schenkers. One is from a standalone compile with out/bin/lilypond and the other is from the docs. Both are from the same computer, same libraries, same git version, fresh build dir, etc. The only difference is whether it comes from "make doc" or from the raw command-line. Attachments: bach-schenker-standalone.ps 311 KB bach-schenker-docs.ps 260 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Updates: Status: Started Labels: Patch-new Comment #5 on issue 1633 by reinhold...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 I have finally been able to reproduce the problem and track down its cause: "make doc" seems to clear the LANG env variable, which causes glib to think it is in some strange (ANSI_X3.4-1968) locale. In this locale, all accented characters in the input string are illegal, so any conversion to utf-16be will fail! However, the input string is actually in UTF-8 (lilypond files are by definition in UTF-8). The solution is to hardcode the UTF-8 locale rather than using the system's locale setting. Patch is up for review at: http://codereview.appspot.com/4449061 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Updates: Labels: -Patch-new Patch-review Comment #6 on issue 1633 by colinpkc...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 Patch has whitespace errors, but allows me to build docs again. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Updates: Status: Fixed Owner: reinhold...@gmail.com Labels: -Patch-review fixed_2_15_0 Comment #7 on issue 1633 by carl.d.s...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 Pushed in commit fa5f3e51c87a5bf90f0bfac5b957ae26403e5c83 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Updates: Labels: backport Comment #8 on issue 1633 by percival.music.ca: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Updates: Labels: -backport fixed_2_13_62 Comment #9 on issue 1633 by carl.d.s...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 Backported. Two commits: d6fcf3af68676af106c285919b15050c44ed36c8 aa730216358403d7a94ff54195de9f4dfd27f402 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Updates: Status: Verified Comment #10 on issue 1633 by colinpkc...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 Verified 2.13.62 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Comment #11 on issue 1633 by carl.d.s...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 Backported the third commit as well. 03ec2b777e64d65be50f03d18f64ba642a9c1c9c ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Updates: Status: Fixed Comment #12 on issue 1633 by percival.music.ca: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 Colin: with all the confusion about branches, I think we should get stricter about verifying. The guidelines have changed: http://lilypond.org/doc/v2.13/Documentation/contributor/bug-squad-checklists it says "Issues to verify: try to reproduce the bug with the latest official GUB version". Since there is no official GUB 2.13.62, this issue cannot be tested yet. This distinction between git master and the latest official GUB build is important, because a bug could be fixed in git master but something could go wrong when backporting it to 2.13.x. 2.13.62 might occur later this week, or it might be on 24 May. Either way, this issue cannot be verified until 2.13.62 is released. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Updates: Status: Verified Comment #13 on issue 1633 by colinpkc...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 Verified 2.15.0 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Updates: Status: Fixed Comment #14 on issue 1633 by colinpkc...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 Unverified in 2.13.61 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Comment #15 on issue 1633 by colinpkc...@gmail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 Attempting to verify with 2.13.62 d/source and build today. Make doc fails with: home/colin/lilypond-2.13.62/build/Documentation/out/notation/fretted-strings. texi /home/colin/lilypond-2.13.62/build/Documentation/out/notation/fretted-strings.t exi:32: I can't find file `02/lily-51d288d6-systems.texi'. @temp ->@input 02/lily-51d288d6-systems.texi @includezzz ...and @input #1 }@expandafter }@temp @popthisfilestack l.32 @include 02/lily-51d288d6-systems.texi (Press Enter to retry, or Control-D to exit) Please type another input file name /home/colin/lilypond-2.13.62/build/Documentation/out/notation/fretted-strings.t exi:32: Emergency stop. @temp ->@input 02/lily-51d288d6-systems.texi @includezzz ...and @input #1 }@expandafter }@temp @popthisfilestack l.32 @include 02/lily-51d288d6-systems.texi /home/colin/lilypond-2.13.62/build/Documentation/out/notation/fretted-strings.t exi:32: ==> Fatal error occurred, no output PDF file produced! Transcript written on notation.log. /usr/bin/texi2dvi: pdfetex exited with bad status, quitting. make[2]: *** [out-www/notation.pdf] Error 1 rm out-www/weblinks.itexi make[2]: Leaving directory `/home/colin/lilypond-2.13.62/build/Documentation' make[1]: *** [WWW-1] Error 2 make[1]: Leaving directory `/home/colin/lilypond-2.13.62/build' make: *** [doc-stage-1] Error 2 The file exists in /build/out/lybook-db/02 and seems identical to the same file in other source directories. For greater clarity: I downloaded the source tarball for 2.13.62, unzipped into a new folder and did the usual ./autogen.sh --noconfigure, mkdir build, cd build, ../configure. Everyting looking normal, I did make -s QUIIET_BUILD=1, then make -s QUIET_BUILD=1 doc and the error occurred, and does so consistently. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Comment #16 on issue 1633 by percival.music.ca: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 hmm. The actual error would have occurred 100-1000 lines above the bit that you quoted -- when the computer tried to compile 02/lily-51d288d6.ly it would have died with some message. Unfortunately, finding such messages in the huge amount of output from 'make doc' is hard, I know... :( If only we had some way of isolating the lilypond console output from each .ly file we tried to compile as part of 'make doc'. ;) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Comment #17 on issue 1633 by philehol...@googlemail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 As Graham knows, I'm working my way through make doc, working out what it does and how to reduce the volume of information. The simplest way to debug this sort of problem is first to try make doc &> ../MakeDoc.txt, then cd .. and grep -e 51d288d6 MakeDoc.txt. If this doesn't provide enough info, then make -d doc also provides make debug info. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
On 11-05-30 05:06 AM, lilyp...@googlecode.com wrote: Comment #17 on issue 1633 by philehol...@googlemail.com: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 As Graham knows, I'm working my way through make doc, working out what it does and how to reduce the volume of information. The simplest way to debug this sort of problem is first to try make doc &> ../MakeDoc.txt, then cd .. and grep -e 51d288d6 MakeDoc.txt. If this doesn't provide enough info, then make -d doc also provides make debug info. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond Still tracking this one down. the make doc &>../MakeDoc.txt gave a different, but still fatal error, so I rebuilt everything, ran it again and got the original error. Colin -- The test of our progress is not whether we add more to the abundance of those who have much, it is whether we provide enough for those who have too little. -Franklin D. Roosevelt, 32nd US President (1882-1945) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
"Colin Campbell" wrote in message news:4de45ab7.8080...@shaw.ca... Still tracking this one down. the make doc &>../MakeDoc.txt gave a different, but still fatal error, so I rebuilt everything, ran it again and got the original error. If you open MakeDoc.txt, you can search for the actual cause of the error - this is easier than trying to find it in a terminal window. -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
On 11-05-31 03:06 AM, Phil Holmes wrote: "Colin Campbell" wrote in message news:4de45ab7.8080...@shaw.ca... Still tracking this one down. the make doc &>../MakeDoc.txt gave a different, but still fatal error, so I rebuilt everything, ran it again and got the original error. If you open MakeDoc.txt, you can search for the actual cause of the error - this is easier than trying to find it in a terminal window. I've got two versions of the output, Phil: one which reproduces the original fail and another which fails differently, so with some judicious use of grep, I ought to find a common element. I'm off to the office today, but I hope to get in a bit of dump-busting this evening. FWIW, make doc runs fine in my lilypond-git folder, so I'm confident of my build environment. Colin -- The test of our progress is not whether we add more to the abundance of those who have much, it is whether we provide enough for those who have too little. -Franklin D. Roosevelt, 32nd US President (1882-1945) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile
Updates: Status: Verified Comment #18 on issue 1633 by percival.music.ca: pdf utf-16be breaks doc compile http://code.google.com/p/lilypond/issues/detail?id=1633 I can confirm that stable/2.14 can build the docs, both "naturally" and in GUB. If you have any problems building master, please report it and we'll make a new issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
