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,
Colin Campbell c...@shaw.ca 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
On 11-05-31 03:06 AM, Phil Holmes wrote:
Colin Campbell c...@shaw.ca 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
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
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
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
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:
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
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
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:
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
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
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
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
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
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.
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
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
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
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
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...
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
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
23 matches
Mail list logo
