Re: CG addition about Git pulling
Mark Polesky wrote Wednesday, January 06, 2010 4:18 AM Trevor Daniels wrote: The section headings need to make it clearer what audience is being addressed. Perhaps Summary for experienced Unix developers Full details for new contributors Then of course there is a lot more to add to provide "full details". But that can come later. Well, this is just the introduction. Full details will come in the chapter on Git. In that case I don't see the point of two separate sections. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Problems with git cl
Hello all, I have done some work to issue 659. I have drwan the alternate segno symbol and in addition, I'll provide new bar commands for easier use. But I don't manage to upload it to rietveld. 1) I have a google account 2) I have downloaded git-cl 3) I have a branch called "varsegno" in my local git repository I did $ git add ... the files, then $ git commit, then $ git format-patch origin and afterwards $git cl upload which I obtained from gitk & I was asked to edit the message for the code review, but then it stops with No output from ['git', 'diff', '--no-ext-diff', '--full-index', '72a4d16977328a91ceb2b83b0a4d09d750129c26', '-M'] I think I just have overlooked the obvious somewhere. Can someone tell me what am I doing wrong? Thanks in advance Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: bends: pre-implementation issues
Han-Wen Nienhuys schrieb: On Tue, Jan 5, 2010 at 5:36 PM, Marc Hohl wrote: Han-Wen Nienhuys schrieb: I am confused here. Are you trying to implement the symbols that are on the tab staff, or on the normal notation? Both. But first, I want to concentrate on the pointed slurs in the normal notation, make that the default for normal staves *and* tablature and then (as I wouldnt bother with the slurs at all, not in the last part because your bends will likely break if someone ever decides to refactor the slur code. Ok. Just write a simple grob that is composed of two line segments to make the pointed bend. Have you already thought of how the spanner should behave when it crosses a line break? @ David: Can you give us a small example of how a bend across a line break would look like? (I know that strings can break after excessive bends, but that's another issue :-) You'll probably need entirely different code for the tab version, including different grob code, and a different engraver. I recommend worrying about that once the pointed-brace version is completely working. Yes, I didn't plan to do all at once, but I wanted to show where the road will eventually lead to. Thanks for your hints! Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Interrupted builds: gs should remove broken output? [Re: [opensuse-contrib] lilypond]
On 01/05/2010 04:10 PM, Jan Nieuwenhuizen wrote:
> Op dinsdag 05-01-2010 om 16:00 uur [tijdzone +0200], schreef Dave
> Plater:
>
>> On 01/05/2010 03:16 PM, Jan Nieuwenhuizen wrote:
>>
>>> Op dinsdag 05-01-2010 om 11:38 uur [tijdzone +0200], schreef Dave
>>> Plater:
>>>
>
>> "/usr/src/packages/BUILD/lilypond-2.12.3/out/lybook-db/snippet-names--7471402555679770406.ly"
>>
>> Can you make anything of this?
>>
> Yes, look earlier in the log and you'll most probably see
> the gs segfault that I mailed and reported this morning.
>
> The trouble is that when gs fails it [may] still produce
> a .pdf which is not removed by gs or the current build system.
>
> Possibly our postscript->pdf or postscript->png functions
> should remove any leftovers of what they're building when
> they exit, although I think this is something that should
> be fixed in gs.
>
> Greetings,
> Jan.
>
>
I made a log of the local rpmbuild of lilypond docs but I unfortunately
mixed up my redirectors and ended up with std error only in the rpmbuild
log, busy making a new one. The only real differences I've picked up so
far is that build service drops -g and -m64 from it's $RPM_OPT_FLAGS. Do
you get a successful build using my spec file with rpmbuild locally.
I've dropped all the patches and the doc tarball and you can comment out
"Source3: changelog" as it's not needed for "rpmbuild -bc". I have
openSUSE 11.2 x86_64 on my box but build service fails to compile the
docs on 11.0 through to factory. I've attached lilypond.spec.
Thanks
Dave P
# spec file for package lilypond (Version 2.12.3)
#
# Copyright (c) 2009 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.
# Please submit bugfixes or comments via http://bugs.opensuse.org/
#
Name: lilypond
BuildRequires: bison fdupes
BuildRequires: flex
BuildRequires: freetype2-devel
BuildRequires: emacs-nox
BuildRequires: gcc-c++
BuildRequires: zypper
BuildRequires: ghostscript-fonts-std >= 8.62-66.1
BuildRequires: ghostscript-library >= 8.62-66.1
BuildRequires: gettext-devel >= 0.17
BuildRequires: guile-devel >= 1.8.2
BuildRequires: info
# openSUSE bug: guile-devel should depend on libtool/libltdl-devel
BuildRequires: libtool
BuildRequires: netpbm
BuildRequires: ImageMagick
BuildRequires: pango-devel
BuildRequires: python-devel >= 2.4
BuildRequires: python-xml
BuildRequires: scrollkeeper
BuildRequires: fontforge >= 20060125
BuildRequires: rsync
BuildRequires: texinfo >= 4.12
#BuildRequires: t1utils >= 1.33 # ugh, LilyPond recommends 1.33!
BuildRequires: t1utils >= 1.26
BuildRequires: texlive-devel texlive-latex texlive-metapost
BuildRequires: zip
%define info yes
License:GPL v2
Group: Productivity/Publishing/Other
Requires: fontconfig >= 2.2
Requires: guile >= 1.8.2
Requires: ghostscript-library >= 8.60
Requires: pango >= 1.12
Requires: python >= 2.4
AutoReqProv:on
Summary:Music Typesetter
Version:2.12.3
Release:0
Url:http://lilypond.org
Source:
http://lilypond.org/download/sources/v2.12/%{name}-%{version}.tar.bz2
# Amazing, rpmlint has a broken rule to check for gzipping of info
# pages. You'd almost think someone really does not *want* to support
# images in info :-)
#Source1:%{name}-2.12.2-rpmlintrc
#Source2:%{name}-%{version}-1.documentation.tar.bz2
Source3:changelog
#Remove dangling symlink from documentation created by fdupes
#Patch0:lilypond-2.12.3-COPYING.patch
#patch info files dir info
#Patch1:lilypond-learning.patch
#Patch2:lilypond-program.patch
BuildRoot: %{_tmppath}/%{name}-%{version}-build
PreReq: %install_info_prereq /usr/bin/touch /usr/bin/sed
%description
LilyPond is a music typesetter, an automated engraving system. It
produces beautiful sheet music using a high level description file as input.
LilyPond supports many forms of music notation constructs, including
chord names, drum notation, figured bass, grace notes, guitar tablature,
modern notation (cluster notation and rhythmic grouping), tremolos,
(nested) tuplets in arbitrary ratios, and more.
LilyPond's text-based music input language support can integrate into
LaTeX, HTML and Texinfo seamlessly, allowing single sheet music
or musicological treatises to be written from a single source. Form and
content are separate, and with LilyPond's expert automa
Re: CG addition about Git pulling
Trevor Daniels wrote: >>> Summary for experienced Unix developers >>> Full details for new contributors >>> >>> Then of course there is a lot more to add to provide >>> "full details". But that can come later. >> >> Well, this is just the introduction. Full details will >> come in the chapter on Git. > > In that case I don't see the point of two separate > sections. Me neither! Hmm If I recall, someone suggested it back in December and then someone else said it was a good idea. So I conceded. (: http://lists.gnu.org/archive/html/lilypond-devel/2009-12/msg00710.html - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problems with git cl
Am Mittwoch, 6. Januar 2010 09:45:20 schrieb Marc Hohl: > the files, then > > $ git commit, > > then > > $ git format-patch origin That's not needed for git-cl > and afterwards > > $git cl upload > > which I obtained from gitk & Ah, so there's the misconception: git-cl does NOT upload the given commit, but rather upload the diff between the given revision and the current state! Since you give the revision number of the current state, there are no changes to be uploaded! A typical call to git-cl is (to upload all changes compared to the laster git master) git cl upload origin/master or (to upload only the last commit) git-cl upload HEAD^1 -- -- 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 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problems with git cl
Reinhold Kainhofer schrieb: Am Mittwoch, 6. Januar 2010 09:45:20 schrieb Marc Hohl: the files, then $ git commit, then $ git format-patch origin That's not needed for git-cl and afterwards $git cl upload which I obtained from gitk & Ah, so there's the misconception: git-cl does NOT upload the given commit, but rather upload the diff between the given revision and the current state! Since you give the revision number of the current state, there are no changes to be uploaded! A typical call to git-cl is (to upload all changes compared to the laster git master) git cl upload origin/master or (to upload only the last commit) git-cl upload HEAD^1 Hello Reinhold, works like a charm now (see my post on -devel about issue 659)! Thanks for your advice! Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Patch: issue #659
Hello all, I've just posted a patch for the alternate segno sign. To use the new symbol stored at scripts.varsegno, I have adapted the arguments for the \bar command. To start a sengo part, you can use \bar ".§" or \bar "§" at the end of the segno part, use \bar "§.". The difference between ".§" and "§." lies in the behavior at line breaks. There is one problem I didn't manage to solve: I had to shrink the width of the character to 0 to place it between the double bar lines; this works but has the drawback that notes are too close to the segno bar. How can I solve this? Thanks, Marc http://codereview.appspot.com/181144 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problems with git cl
On 1/6/10 1:45 AM, "Marc Hohl" wrote: > Hello all, > > I have done some work to issue 659. I have drwan the alternate segno > symbol and > in addition, I'll provide new bar commands for easier use. > > But I don't manage to upload it to rietveld. > > 1) I have a google account > 2) I have downloaded git-cl > 3) I have a branch called "varsegno" in my local git repository > > I did > > $ git add ... > > the files, then > > $ git commit, > > then > > $ git format-patch origin > > and afterwards > > $git cl upload > > which I obtained from gitk & > > I was asked to edit the message for the code review, but then it stops with > > No output from ['git', 'diff', '--no-ext-diff', '--full-index', > '72a4d16977328a91ceb2b83b0a4d09d750129c26', '-M'] > > I think I just have overlooked the obvious somewhere. Can someone tell > me what am I doing wrong? It appears to me that you are using the SHA1 of HEAD, not the SHA1 of the parent of HEAD If you only have a single commit on varsegno, then you can just do git-cl upload HEAD^ Your error message indicates that there is no difference between the HEAD of the branch you are on and the commit whose SHA1 you entered in the git-cl command. You can test this out before using git-cl by doing git diff and seeing what is reported. HTH, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problems with git cl
Carl Sorensen schrieb: [...] You can test this out before using git-cl by doing git diff and seeing what is reported. This is very helpful - thanks! Marc HTH, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Issue 659: alternate segno symbol (issue181144)
I haven't tried this out, but some things simply jump out..
http://codereview.appspot.com/181144/diff/1/3
File lily/bar-line.cc (right):
http://codereview.appspot.com/181144/diff/1/3#newcode96
lily/bar-line.cc:96: Stencil segno = Font_interface::get_default_font
(me)->find_by_name ("scripts.varsegno");
You need this stencil only in that one if clause below... No need to
allocate it for each and every compound bar line. I would move it
directly before the m.add_at_edge below.
http://codereview.appspot.com/181144/diff/1/3#newcode121
lily/bar-line.cc:121: str = "$";
Are you sure you want $ and not §?
http://codereview.appspot.com/181144/diff/1/3#newcode385
lily/bar-line.cc:385: " @code{|.|}, @code{:}, @code{dashed}, code{§} and
@code{'}.\n"
How easy is it to produce a § on an US keyboard? Here in Europe it's
easy, but I don't think that key is on an English (non-international)
keyboard by default.
http://codereview.appspot.com/181144
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Issue 659: alternate segno symbol (issue181144)
reinhold.kainho...@gmail.com schrieb:
I haven't tried this out, but some things simply jump out..
http://codereview.appspot.com/181144/diff/1/3
File lily/bar-line.cc (right):
http://codereview.appspot.com/181144/diff/1/3#newcode96
lily/bar-line.cc:96: Stencil segno = Font_interface::get_default_font
(me)->find_by_name ("scripts.varsegno");
You need this stencil only in that one if clause below... No need to
allocate it for each and every compound bar line. I would move it
directly before the m.add_at_edge below.
Done.
http://codereview.appspot.com/181144/diff/1/3#newcode121
lily/bar-line.cc:121: str = "$";
Are you sure you want $ and not §?
No, I wasn't :-) Just a type which remained undetected during the
compilation
of the regression test file.
Done.
http://codereview.appspot.com/181144/diff/1/3#newcode385
lily/bar-line.cc:385: " @code{|.|}, @code{:}, @code{dashed}, code{§} and
@code{'}.\n"
How easy is it to produce a § on an US keyboard? Here in Europe it's
easy, but I don't think that key is on an English (non-international)
keyboard by default.
After consulting wikipedia for several keyboard layouts, you have
convinced me.
I changed the § sign to an uppercase S, which should be accessible from any
latin keyboard.
http://codereview.appspot.com/181144
Thanks!
Marc
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Need help with building docs on openSUSE build service
Hi, I maintain lilypond on openSUSE and am having a problem compiling the documentation, a local build with rpmbuild succeeds but a chrooted build fails seemingly on a ghostscript command. I've come to the conclusion, after many long builds (one and a half hours locally and half hour online), that something that ghostscript needs isn't installed in the chrooted system or lilypond doesn't compile properly due to something missing in the chrooted system. The first doc compile error I hit which is only in the chrooted builds build log is :- Processing `/usr/src/packages/BUILD/lilypond-2.12.3/input/les-nereides.ly' Parsing...Processing `/usr/src/packages/BUILD/lilypond-2.12.3/input/typography-demo.ly' Parsing... Interpreting music... Interpreting music... Preprocessing graphical objects...[8] Preprocessing graphical objects... programming error: FT_Get_Glyph_Name () error: invalid argument which the successful build has :- Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 page... warning: no PostScript font name for font `/usr/share/fonts/misc/b24.pcf.gz' warning: FreeType face has no PostScript font name Things don't go well in the failed build from there on but continue for quite a while with many "programming error: FT_Get_Glyph_Name () error: invalid argument" errors. At the end of the failed build log I get :- error: failed files: "3f/lily-65a7b1b1.ly" Then, with the plus sign inserted at the begining of the two extra lines fro the successful builds :- e364e.png" -r202 "./03/lily-cabe364e.eps" -c quit'... + Invoking `pngtopnm ./2a/lily-03d90eb9.png.old | pnmscale -reduce 2 2>/dev/null | pnmtopng -compression 9 2>/dev/null > ./2a/lily-03d90eb9.png'... + Invoking `gs -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 -dNOPAUSE -sDEVICE=png16m -sOutputFile="./03/lily-cabe364e.png" -r202 "./03/lily-cabe364e.eps" -c quit'... Invoking `pngtopnm ./03/lily-cabe364e.png.old | pnmscale -reduce 2 2>/dev/null | pnmtopng -compression 9 2>/dev/null > ./03/lily-cabe364e.png'... Invoking `gs -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 -dNOPAUSE -sDEVICE=png16m -sOutputFile="./f3/lily-56ccab9f.png" -r202 "./f3/lily-56ccab9f.eps" -c quit'... Invoking `pngtopnm ./f3/lily-56ccab9f.png.old | pnmscale -reduce 2 2>/dev/null | pnmtopng -compression 9 2>/dev/null > ./f3/lily-56ccab9f.png'... Invoking `gs -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 -dNOPAUSE -sDEVICE=png16m -sOutputFile="./f4/lily-2976c566.png" -r202 "./f4/lily-2976c566.eps" -c quit'... Invoking `pngtopnm ./f4/lily-2976c566.png.old | pnmscale -reduce 2 2>/dev/null | pnmtopng -compression 9 2>/dev/null > ./f4/lily-2976c566.png'... Invoking `gs -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 -dNOPAUSE -sDEVICE=png16m -sOutputFile="./23/lily-236742d0.png" -r202 "./23/lily-236742d0.eps" -c quit'... Invoking `pngtopnm ./23/lily-236742d0.png.old | pnmscale -reduce 2 2>/dev/null | pnmtopng -compression 9 2>/dev/null > ./23/lily-236742d0.png'... Invoking `gs -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 -dNOPAUSE -sDEVICE=png16m -sOutputFile="./66/lily-7ec68366.png" -r202 "./66/lily-7ec68366.eps" -c quit'... Invoking `pngtopnm ./66/lily-7ec68366.png.old | pnmscale -reduce 2 2>/dev/null | pnmtopng -compression 9 2>/dev/null > ./66/lily-7ec68366.png'... given value (in dpi). safe (#f) Run in safer mode. separate-log-files (#f) For input files `FILE1.ly', `FILE2.ly', ... output log data to files `FILE1.log', `FILE2.log', ... show-available-fonts (#f) List available font names. strict-infinity-checking (#f) Force a crash on encountering Inf and NaN floating point exceptions. strip-output-dir (#f) Don't use directories from input files while constructing output file names. trace-memory-frequency (#f) Record Scheme cell usage this many times per second. Dump results to `FILE.stacks' and `FILE.graph'. trace-scheme-coverage (#f) Record coverage of Scheme files in `FILE.cov'. verbose (#t)Value of the --verbose flag (read-only). command failed: /usr/src/packages/BUILD/lilypond-2.12.3/out/bin/lilypond -I ./ -I ./out-www -I ../../input -I ../../input/lsr/ -I ../../input/regression/ -I ../../input/manual/ -I ../../input/tutorial/ -I /usr/src/packages/BUILD/lilypond-2.12.3/mf/out/ -I /usr/src/packages/BUILD/lilypond-2.12.3/mf/out/ -I /usr/src/packages/BUILD/lilypond-2.12.3/input/manual -I /usr/src/packages/BUILD/lilypond-2.12.3/Documentation -dbackend=eps --formats=ps,png,pdf -dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitlefr --header=doctitlees --header=doctitlede --header=doctitleja --header=texidoc --header=texidocfr --head
Re: Need help with building docs on openSUSE build service
On 01/07/2010 08:31 AM, Dave Plater wrote: > Hi, I maintain lilypond on openSUSE and am having a problem compiling > the documentation, a local build with rpmbuild succeeds but a chrooted > build fails seemingly on a ghostscript command. I've come to the > conclusion, after many long builds (one and a half hours locally and > half hour online), that something that ghostscript needs isn't installed > in the chrooted system or lilypond doesn't compile properly due to > something missing in the chrooted system. > The first doc compile error I hit which is only in the chrooted builds > build log is :- > Processing `/usr/src/packages/BUILD/lilypond-2.12.3/input/les-nereides.ly' > Parsing...Processing > `/usr/src/packages/BUILD/lilypond-2.12.3/input/typography-demo.ly' > Parsing... > Interpreting music... > Interpreting music... > Preprocessing graphical objects...[8] > Preprocessing graphical objects... > programming error: FT_Get_Glyph_Name () error: invalid argument > > which the successful build has :- > Preprocessing graphical objects... > Finding the ideal number of pages... > Fitting music on 1 page... > warning: no PostScript font name for font `/usr/share/fonts/misc/b24.pcf.gz' > warning: FreeType face has no PostScript font name > > Things don't go well in the failed build from there on but continue for > quite a while with many "programming error: FT_Get_Glyph_Name () error: > invalid argument" errors. > At the end of the failed build log I get :- > error: failed files: "3f/lily-65a7b1b1.ly" > Then, with the plus sign inserted at the begining of the two extra lines > fro the successful builds :- > e364e.png" -r202 "./03/lily-cabe364e.eps" -c quit'... > + Invoking `pngtopnm ./2a/lily-03d90eb9.png.old | pnmscale -reduce 2 > 2>/dev/null | pnmtopng -compression 9 2>/dev/null > > ./2a/lily-03d90eb9.png'... > + Invoking `gs -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 > -dNOPAUSE -sDEVICE=png16m -sOutputFile="./03/lily-cabe364e.png" -r202 > "./03/lily-cabe364e.eps" -c quit'... > Invoking `pngtopnm ./03/lily-cabe364e.png.old | pnmscale -reduce 2 > 2>/dev/null | pnmtopng -compression 9 2>/dev/null > > ./03/lily-cabe364e.png'... > Invoking `gs -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 > -dNOPAUSE -sDEVICE=png16m -sOutputFile="./f3/lily-56ccab9f.png" -r202 > "./f3/lily-56ccab9f.eps" -c quit'... > Invoking `pngtopnm ./f3/lily-56ccab9f.png.old | pnmscale -reduce 2 > 2>/dev/null | pnmtopng -compression 9 2>/dev/null > > ./f3/lily-56ccab9f.png'... > Invoking `gs -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 > -dNOPAUSE -sDEVICE=png16m -sOutputFile="./f4/lily-2976c566.png" -r202 > "./f4/lily-2976c566.eps" -c quit'... > Invoking `pngtopnm ./f4/lily-2976c566.png.old | pnmscale -reduce 2 > 2>/dev/null | pnmtopng -compression 9 2>/dev/null > > ./f4/lily-2976c566.png'... > Invoking `gs -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 > -dNOPAUSE -sDEVICE=png16m -sOutputFile="./23/lily-236742d0.png" -r202 > "./23/lily-236742d0.eps" -c quit'... > Invoking `pngtopnm ./23/lily-236742d0.png.old | pnmscale -reduce 2 > 2>/dev/null | pnmtopng -compression 9 2>/dev/null > > ./23/lily-236742d0.png'... > Invoking `gs -dEPSCrop -dGraphicsAlphaBits=4 -dTextAlphaBits=4 > -dNOPAUSE -sDEVICE=png16m -sOutputFile="./66/lily-7ec68366.png" -r202 > "./66/lily-7ec68366.eps" -c quit'... > Invoking `pngtopnm ./66/lily-7ec68366.png.old | pnmscale -reduce 2 > 2>/dev/null | pnmtopng -compression 9 2>/dev/null > > ./66/lily-7ec68366.png'... > given value (in dpi). > safe (#f) Run in safer mode. > separate-log-files (#f) For input files `FILE1.ly', `FILE2.ly', ... > output log data to files `FILE1.log', > `FILE2.log', ... > show-available-fonts (#f) > List available font names. > strict-infinity-checking (#f) > Force a crash on encountering Inf and NaN > floating point exceptions. > strip-output-dir (#f) Don't use directories from input files while > constructing output file names. > trace-memory-frequency (#f) > Record Scheme cell usage this many times per > second. Dump results to `FILE.stacks' and > `FILE.graph'. > trace-scheme-coverage (#f) > Record coverage of Scheme files in `FILE.cov'. > verbose (#t)Value of the --verbose flag (read-only). > > command failed: /usr/src/packages/BUILD/lilypond-2.12.3/out/bin/lilypond > -I ./ -I ./out-www -I ../../input -I ../../input/lsr/ -I > ../../input/regression/ -I ../../input/manual/ -I ../../input/tutorial/ > -I /usr/src/packages/BUILD/lilypond-2.12.3/mf/out/ -I > /usr/src/packages/BUILD/lilypond-2.12.3/mf/out/ -I > /usr/src/packages/BUILD/lilypond-2.12.3/input/manual -I > /usr/src/packages/BUILD/lilypond-2.12.
