Re: LilyPond doesn't work. Help please?
Please rerun setup.exe and make sure to follow the instructions at http://lilypond.org/web/download/windows.html on how to select the lilypond package. Note that setup.exe will only download the packages that it did not install the previous time, so you have not wasted modem time. /Mats Frank D wrote: Gentlemen, I just downloaded and _thought_ I installed LilyPond on my PC (Windows XP Pro, 700-MHz). It took about an hour and a half with a 56-K Modem. However, I have no test.log and the test.ly file did not open. Obviously I did not install the LilyPond package correctly (or at all). I believe I've followed the procedure correctly, but it doesn't work. I can find no "install.exe" file or similar file, so I'm stumped. Can you help me? Thank you. Frank C. Dauenhauer ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Making Large-Print Music Again
Ruven Gottlieb wrote: Mats Bengtsson wrote: Ferenc Wagner wrote: Ruven Gottlieb <[EMAIL PROTECTED]> writes: I see there is a file called titledefs.tex in /usr/share/lilypond/2.2.0/tex/ I don't want to hack on that if I can help it, rather I'd like to be able to have lilypond use one I specify, or the equivalent Right Thing. The TEXMF environmental variable is set in lilypond-profile or lilypond-login. Change it to your liking. Well, maybe setting TEXINPUTS to a directory of yours is enough. Yes, try setting TEXINPUTS to your/own/directory: Note the colon at the end, which tells TeX to look also in the default paths (but first look in your own directory). OK, the 2.x manual says lilypond-profile and lilypond-login are located in buildscripts/out/ . Neither the Fedora Core 1 distribution nor the source dist contain these scripts or this directory. Are they created during make? The idea of setting TEXINPUTS is that you don't have to do any changes at all to the system wide lilypond-profile file. Instead, you just set TEXINPUTS in your own ~/.profile. (For the record, the files are created during make and are probably installed in /etc/profile.d/ on your machine). > I tried to configure/make the source, but I got an error message: ERROR: Please install required programs: echo no guile-config >= 1.6 (installed:) I have guile 1.6 installed. You probably need a package named something like guile-devel that contains the include files and lib files to be used at compile time. I think the titling layout ought to be more accessible and configurable, optimally some sort of template that can be included or referenced on a per-score basis. Not only for my large print project, but for different title layouts too. The lilypond script is only intended to give a decent layout for normal cases. If you want more freedom to adjust titling and page layout, I recommend to use lilypond-book instead. /Mats ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Making Large-Print Music Again
Ruven Gottlieb <[EMAIL PROTECTED]> writes: > Mats Bengtsson wrote: > >> Ferenc Wagner wrote: >> >>> Ruven Gottlieb <[EMAIL PROTECTED]> writes: >>> I see there is a file called titledefs.tex in /usr/share/lilypond/2.2.0/tex/ I don't want to hack on that if I can help it, rather I'd like to be able to have lilypond use one I specify, or the equivalent Right Thing. >>> >>> The TEXMF environmental variable is set in lilypond-profile >>> or lilypond-login. Change it to your liking. Well, maybe >>> setting TEXINPUTS to a directory of yours is enough. >> >> Yes, try setting TEXINPUTS to >> your/own/directory: >> Note the colon at the end, which tells TeX to look also in the >> default paths (but first look in your own directory). > > OK, the 2.x manual says lilypond-profile and > lilypond-login are located in buildscripts/out/ . Neither > the Fedora Core 1 distribution nor the source dist contain > these scripts or this directory. Are they created during > make? Yes. Files in out and out-www directories are all generated. But packages should contain these; you found a packaging mistake. > ERROR: Please install required programs: echo no > guile-config >= 1.6 (installed:) > > I have guile 1.6 installed. You also need the guile-1.6-devel package (or similar, and maybe lots of others) if you really want to compile LilyPond. > I think the titling layout ought to be more accessible and > configurable, optimally some sort of template that can be > included or referenced on a per-score basis. Have you considered using lilypond-book? All the power of TeX is at your service. -- Feri. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Rasgueado notation in LilyPond?
On Tuesday 13 April 2004 01:21, Gunther Strube wrote: > Hi, > > >What is the difference with an arpeggio with a direction? Have you > > seen: > > > > > > http://www.lilypond.org/doc/v2.2/Documentation/user/out-www/lilypon > >d/Arpeggio.html > > > >I cannot find Rasgueado in the music glossary. > > That's it! > > I forgot that it was used as arpeggio notation for piano. The arrows are also sometimes used to indicate how to play a chord on monophonic instruments, and the arpeggio notation sometimes has an arrowhead too. It would be very unfortunate to treat these like grace notes in midi, because the last chord or note should be accented, not the first. It would be better yet to be able to choose between the two behaviors, but almost always other music, such as Mozart's "Alla Turca", should be performed the same way, toward the beat. If you don't believe me, try it. > (beginning with ring-finger and ending with the > thumb)- in other words the Rasgueado... Ending with the index. The thumb down (up arrow) in this circumstance might very rarely be found on the last chord of a piece, never anywhere else. The standard notation is so bad (too many vertical lines) that you might take a look at tengtr.pdf on my website. My way is easier to note and much easier to read. daveA -- Paying more at the gas pump? Bush's Oil Sheikh Buddies, who support Al Qaeda, Palestinian terrorists, & hate-U.S. school systems everywhere, need more of your money now to arm and pay Iraqis to kill Americans. D. Raleigh Arnold dra@ (http://www.) openguitar.com [EMAIL PROTECTED] ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Newbie: Getting started with lilypond-book
Ben, thank for letting me know about the attachments not being allowed. I didn't know
that. I thought I was making it easier for anyone to help me.
I did try to change the size, as I thought was shown in the manual, but didn't see any
change on the output.
I've cut and pasted the three files in at the end of this message. Cut between lines
"==" to reassemble them.
Thank you all for your patience and suggestions.
>>> Ben Crowell <[EMAIL PROTECTED]> 04/10/04 05:56PM >>>
I don't think this list allows attachments, so we can't see your latex code.
The lilypond-book manual shows examples of how to change the size. Did that
not work for you?
original message:
I'm sorry to ask this, but I've just gotten frustrated by working with this over the
last two hours, and wonder if someone can get me unstuck.
I'm trying to produce two short tunes (for contra dance music) on the same page. I've
created the two tunes in two separate files, which I've attached. I've also attached a
file JuliaDelaney_Spootiskerry.tex, which I'm trying to use in lilypond-book to
generate the file.
My sequence of commands is:
emacs JuliaDelaney_Spootiskerry.tex
lilypond-book --outdir=out JuliaDelaney_Spootiskerry.tex
cd out
latex JuliaDelaney_Spootiskerry.latex
dvips -o JuliaDelaney_Spootiskerry.ps JuliaDelaney_Spootiskerry
I think the version I've attached will actually generate a viewable .ps file, but I
have two problems with it:
1. I want to reduce the font size, so that both tunes fit on one side of a page, and
2. I want to print out the Title information, just as if I generated separate .pdf
files for each tune, and embedded them in a single, one-page document. I read
somewhere that the footer information would be dropped in this case, which is exactly
what I would prefer.
Would someone please show me how to edit my JuliaDelaney_Spootiskerry.tex file to fix
these two problems?
My assumption so far is that I could create just one file per tune, and then combine
two tunes on a page without changing the individual 'tune-files' through the use of
lilypond-book. Is this a correct assumption?
Thanks so much for your suggestions.
-Kevin Zembower
File JuliaDelaney_Spootiskerry.tex:
==
\documentclass[a4paper]{article}
\begin{document}
\lilypondfile[11pt]{JuliaDelaney.ly}
\lilypondfile[11pt]{Spootiskerry.ly}
\end{document}
==
File JuliaDelaney.ly:
===
\include "paper20.ly"
\paper {
linewidth = 455.244096\pt
}
\version "1.9.8"
\header {
%dedication = "dedication"
title = "Julia Delaney"
%subtitle = "Subtitle"
%subsubtitle = "Subsubtitle"
composer = "Traditional"
%opus = "Opus 0"
opus = "Reel"
%piece = "Piece I"
%instrument = "Instrument"
%arranger = "Engraved by Ed Vanden Bosch and Kevin Zembower"
%poet = "Poet"
%texttranslator = "Translator"
%copyright = "public domain"
%source = "urtext "
%enteredby = "Kevin Zembower"
%maintainerEmail = "[EMAIL PROTECTED]"
%texidoc = "The standard header that ought to be above a file."
tagline = "Engraved by LilyPond, 2.0.0.Engraved by Ed Vanden Bosch and Kevin
ZemboweProduced for the Baltimore Folk Music Society Open Band
(http://www.bfms.org)."
}
melody = \notes \relative c'' {
\property Score.RehearsalMark \override #'molecule-callback =
#(make-molecule-boxer 0.15 0.3 0.3 brew-new-markup-molecule)
\key d \minor
\repeat volta 2 {
\mark "A"
d8 c a g \times 2/3 { f8 g f } c8 f | \times 2/3 { e8 f e } c8 e f d d4 |
d'8 c a g \times 2/3 { f8 g f } c8 f | a d d cis d e f e |
d c a g \times 2/3 { f8 g f } d8 f | \times 2/3 { e8 f e } c8 e f d d4 |
d'8 c a g \times 2/3 { f8 g f } d8 f | a d d cis d2 |
}
\break
\repeat volta 2 {
\mark "B"
f4 f8 e f a g f| \times 2/3 { e8 d c } g8 c a c g4 |
f8 e d e f a g f | e d c a a d d e |
f4 f8 e f a g f | \times 2/3 { e8 d c } g'8 a a a g4 |
f8 e d f e d c a | a d d cis d2 |
}
}
accompaniment = \chords {
}
\score {
<<
\context ChordNames \accompaniment
\context Staff = one {
\property Staff.automaticMelismata = ##t
\melody
}
>>
\paper { }
}
==
File Spootiskerry.ly:
===
\include "paper20.ly"
\paper {
linewidth = 455.244096\pt
}
\version "1.9.8"
\header {
%dedication = "dedication"
title = "Spootiskerry"
%subtitle = "Subtitle"
%subsubtitle = "Subsubtitle"
composer = "Traditional"
%opus = "Opus 0"
opus = "Reel"
%piece = "Piece I"
%instrument = "Instrument"
arranger = "Engraved by Kevin Zembower"
%poet = "Poet"
%texttranslator = "Translator"
%copyright = "public domain"
%source = "urtext "
%enteredby = "Kevin Zembower"
%maintainerEmail = "[EMAIL PROTECTED]"
%texidoc = "The standard header th
Re: Newbie: Getting started with lilypond-book
For the font size, you explicitly specify 20pt size within the .ly files
and this will override the setting added by lilypond-book. Just remove
the line
\include "paper20.ly"
in your .ly files (20pt is the default size anyway).
For the titling, see
http://mail.gnu.org/archive/html/lilypond-user/2004-03/msg00395.html
(you may want to look at the follow-up mails as well).
/Mats
KEVIN ZEMBOWER wrote:
Ben, thank for letting me know about the attachments not being allowed. I didn't know that. I thought I was making it easier for anyone to help me.
I did try to change the size, as I thought was shown in the manual, but didn't see any change on the output.
I've cut and pasted the three files in at the end of this message. Cut between lines "==" to reassemble them.
Thank you all for your patience and suggestions.
Ben Crowell <[EMAIL PROTECTED]> 04/10/04 05:56PM >>>
I don't think this list allows attachments, so we can't see your latex code.
The lilypond-book manual shows examples of how to change the size. Did that
not work for you?
original message:
I'm sorry to ask this, but I've just gotten frustrated by working with this over the last two hours, and wonder if someone can get me unstuck.
I'm trying to produce two short tunes (for contra dance music) on the same page. I've created the two tunes in two separate files, which I've attached. I've also attached a file JuliaDelaney_Spootiskerry.tex, which I'm trying to use in lilypond-book to generate the file.
My sequence of commands is:
emacs JuliaDelaney_Spootiskerry.tex
lilypond-book --outdir=out JuliaDelaney_Spootiskerry.tex
cd out
latex JuliaDelaney_Spootiskerry.latex
dvips -o JuliaDelaney_Spootiskerry.ps JuliaDelaney_Spootiskerry
I think the version I've attached will actually generate a viewable .ps file, but I
have two problems with it:
1. I want to reduce the font size, so that both tunes fit on one side of a page, and
2. I want to print out the Title information, just as if I generated separate .pdf
files for each tune, and embedded them in a single, one-page document. I read
somewhere that the footer information would be dropped in this case, which is exactly
what I would prefer.
Would someone please show me how to edit my JuliaDelaney_Spootiskerry.tex file to fix these two problems?
My assumption so far is that I could create just one file per tune, and then combine two tunes on a page without changing the individual 'tune-files' through the use of lilypond-book. Is this a correct assumption?
Thanks so much for your suggestions.
-Kevin Zembower
File JuliaDelaney_Spootiskerry.tex:
==
\documentclass[a4paper]{article}
\begin{document}
\lilypondfile[11pt]{JuliaDelaney.ly}
\lilypondfile[11pt]{Spootiskerry.ly}
\end{document}
==
File JuliaDelaney.ly:
===
\include "paper20.ly"
\paper {
linewidth = 455.244096\pt
}
\version "1.9.8"
\header {
%dedication = "dedication"
title = "Julia Delaney"
%subtitle = "Subtitle"
%subsubtitle = "Subsubtitle"
composer = "Traditional"
%opus = "Opus 0"
opus = "Reel"
%piece = "Piece I"
%instrument = "Instrument"
%arranger = "Engraved by Ed Vanden Bosch and Kevin Zembower"
%poet = "Poet"
%texttranslator = "Translator"
%copyright = "public domain"
%source = "urtext "
%enteredby = "Kevin Zembower"
%maintainerEmail = "[EMAIL PROTECTED]"
%texidoc = "The standard header that ought to be above a file."
tagline = "Engraved by LilyPond, 2.0.0.Engraved by Ed Vanden Bosch and Kevin ZemboweProduced for the Baltimore Folk Music Society Open Band (http://www.bfms.org)."
}
melody = \notes \relative c'' {
\property Score.RehearsalMark \override #'molecule-callback =
#(make-molecule-boxer 0.15 0.3 0.3 brew-new-markup-molecule)
\key d \minor
\repeat volta 2 {
\mark "A"
d8 c a g \times 2/3 { f8 g f } c8 f | \times 2/3 { e8 f e } c8 e f d d4 |
d'8 c a g \times 2/3 { f8 g f } c8 f | a d d cis d e f e |
d c a g \times 2/3 { f8 g f } d8 f | \times 2/3 { e8 f e } c8 e f d d4 |
d'8 c a g \times 2/3 { f8 g f } d8 f | a d d cis d2 |
}
\break
\repeat volta 2 {
\mark "B"
f4 f8 e f a g f| \times 2/3 { e8 d c } g8 c a c g4 |
f8 e d e f a g f | e d c a a d d e |
f4 f8 e f a g f | \times 2/3 { e8 d c } g'8 a a a g4 |
f8 e d f e d c a | a d d cis d2 |
}
}
accompaniment = \chords {
}
\score {
<<
\context ChordNames \accompaniment
\context Staff = one {
\property Staff.automaticMelismata = ##t
\melody
}
>>
\paper { }
}
==
File Spootiskerry.ly:
===
\include "paper20.ly"
\paper {
linewidth = 455.244096\pt
}
\version "1.9.8"
\header {
%dedication = "dedication"
title = "Spootiskerry"
%subtitle = "Subtitle"
%subsubtitle =
Call for help
Dear LilyPond afficionado, As you might have noticed, LilyPond has been improving at a breakneck speed for the last year, which is a good thing. This email hopes to continue that trend by unleashing an enormous source of development potential, and that is ... You! LilyPond already has seen an increase contributions over the past months, from packagers, bugfixers, proofreaders, etc. We love your help, and we can't have enough of it so we are seeking help. Join LilyPond development for riches, eternal fame, and getting your name in the THANKS file :-) There are plenty of ways to get into the THANKS file, for example, by taking care of documentation, bug reports, releases, etc. We have compiled a list of tasks that we would love to be helped with. Have a look to see if there is something for you! Many of the tasks are not very technical, so don't dismiss yourself too quickly. We have plenty of experience with these tasks, so there is always someone to guide you and get you started. Hopefully, together we can address problems in the LilyPond development process, among others * Stable releases don't happen often enough. * Development is too much centralized. * The learning curve is too steep. The list of tasks is not exhaustive. If you have good ideas on how to get more people involved, or how to use our energy more efficiently, don't hesitate to drop a note on the development mailing list [EMAIL PROTECTED] Of course, if you have an itch to scratch, you can also send patches to this mailinglist :-) What other great plans can you expect from us? We have a roadmap, sort of, which is to implement the following features for the next major release * Support for font-encoding like latin1, cyrillic, etc. * Usable direct postscript output (with titling, and multiple scores). * Optimal page breaking. Of course, the release date depends on how much help we get with all the tasks mentioned below. RELEASE-MEISTER The job of the release-meister is to coordinate releases. Ideally, they would happen less frequently than they do now --perhaps once a month-- but offer a better quality. LilyPond is ready for a release when * The regression test comes out clean * All features work as documented * A new release would offer an improvement over the last one The release-meister keeps an eye on the bugreports and ChangeLog, and has the responsibility to decide when a release is in order. The actual mechanics entail branching CVS, pestering developers for important bug-fixes, creating and uploading the tarball, announcing it on mailing lists, websites, etc. BUILD-MEISTER The responsibility of the build-meister it is to make sure that binary packages of LilyPond are available for all platforms. To this end, the build-meister * Regularly (say, once a week) packages LilyPond CVS for one platform. This is to check for bugs in the installation procedure. * Tries to find people that will build LilyPond packages for other platforms, either for releases or from CVS. * Tries to convince vendors (Fedora, Mandrake, etc.) to put lily in their base distributions. * Maintains the lilypond.org/download/ page. BUG-MEISTER The Bug-meister is the human face behind the collection of LilyPond bugs. He (or she, of course) keeps an eye on bugs in LilyPond, especially those where LilyPond produces incorrect notation or typography. This is a very important job, since good responses to bugreports makes LilyPond look good for struggling users. * He will be reading the bug-lilypond and lilypond-user mailing list, replying to bugreporters and distilling small failure cases for each report. * Every bug goes into a bug-collection. In the collection for each bug, there is - A .ly snippet, trimmed as far as possible. - An image demonstrating the problem. - A description of what is wrong. - Whether the bug concerns a new feature, or breaks existing features. - If the latter, the version number where the bug started manifesting. - The severity of the bug: a bug should get priority if it causes crashes, when there are no workarounds, or if it affects a large number of people. * Periodically (say, every week), the bug-collection is run through LilyPond to determine which problems are still open. * Some bugs, when fixed, should be added as a regression test. * Of course, the bug-meister will pester developers to fix serious bugs. An example of excellent bug-reports is the bug-collection of Werner Lemberg, see for example http://mail.gnu.org/archive/html/lilypond-devel/2004-03/msg00138.html REQUIREMENTS: read email regularly, so bugreports are replied to in a timely fashion. The DOCUMENTATION EDITOR eases LilyPond's learning curve by improving the manual. Specifically, the documentation e
Re: Bagpipe Music and Grace Notes
Hello list, hello Andrew,
You wrote:
> Bagpipe music has tons of grace notes, all of which are printed as 32nd
> notes. The main problem I'm having is with beamed grace notes. The
> stems on groups of grace notes are just a little too short, and
> sometimes the third beam actually collides with note heads. You can see
> this in input/test/bagpipe.ly.
>
> I'd really appreciate help about how to correct this behavior. Thanks
> in advance.
Unfortunately I don't know a global solution, but a local solution would
be par example for the following little code
\score { \notes \relative c'' {
\grace { f64 [ e d c ] } e16 [ d f e ] d [ g f e ] }
}
to put a line before the beamed group like this:
\score { \notes \relative c'' {
\once\override Beam #'positions = #'(5.5 . 4.5)
\grace { f64 [ e d c ] } e16 [ d f e ] d [ g f e ] }
}
For this example it is a better solution, but the vertical positions
determined with "5.5" (beginning) and "4.5" (end) is not relative to the
noteheads, but to the staff, so with changing pitches You have in each
case to change the vertical positions again.
Nevertheless:
Perhaps this is the solution which You was looking for ... :)
Best Regards Roland
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: rest collision
Hello list, hello Stan,
You wrote:
> In the attached example, eighth rests collide with note stems. I'd
> appreciate suggestions about how to make it look better.
>
> The code for the measure(s) is
>
> 8 |
> <<{d8\rest [ c8\rest ]}\\{4 }>> |
> %%% measure 86
> 8
Give the following line just before the rest:
\once\override Score.Rest #'extra-offset = #'(.3 . .3)
If You don't want to type this line before each rest, You can stroke the
"\once":
\override Score.Rest #'extra-offset = #'(.3 . .3)
But this will work on each rest in the whole Score.
So, if You have only many rests to shift with the same numbers, and in
this area is no other rest, You can take the second line, and after this
area You have to give the line
\revert Score.Rest #'extra-offset
so that the following rests are not shifted.
In Your little example it will look as follows:
\override Score.Rest #'extra-offset = #'(.3 . .3)
<<{d8\rest [ c8\rest ]}\\{4 }>> |
> The \rest coding was used to bring the rests down from the note heads.
In case of only one rest-shifting this would not be necessary, You could
shift it as follows:
\once\override Score.Rest #'extra-offset = #'(.3 . -4.1)
<<{r8 [ c8\rest ]}\\{4 }>> |
But if there are many rest-shifings like this, the \rest coding is to
prefer, because of the shifting with \override Score.Rest is relative to
the given note\rest, otherwise the rest's vertical position is
orientated to the note before, and it would be too complicated to set
each different numbers of shifting.
I think, this will help You. :)
Best Regards Roland
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: rest collision
Roland,
Thank you for your reply. I'm very appreciative of the work which has
gone into lilypond to make it so flexible, and of the kindness of those
on the list to beginners such as I.
Stan
On Apr 13, 2004, at 7:12 PM, Roland Goretzki wrote:
Hello list, hello Stan,
You wrote:
In the attached example, eighth rests collide with note stems. I'd
appreciate suggestions about how to make it look better.
The code for the measure(s) is
8 |
<<{d8\rest [ c8\rest ]}\\{4 }>> |
%%% measure 86
8
Give the following line just before the rest:
\once\override Score.Rest #'extra-offset = #'(.3 . .3)
If You don't want to type this line before each rest, You can stroke
the
"\once":
\override Score.Rest #'extra-offset = #'(.3 . .3)
But this will work on each rest in the whole Score.
So, if You have only many rests to shift with the same numbers, and in
this area is no other rest, You can take the second line, and after
this
area You have to give the line
\revert Score.Rest #'extra-offset
so that the following rests are not shifted.
In Your little example it will look as follows:
\override Score.Rest #'extra-offset = #'(.3 . .3)
<<{d8\rest [ c8\rest ]}\\{4 }>> |
The \rest coding was used to bring the rests down from the note heads.
In case of only one rest-shifting this would not be necessary, You
could
shift it as follows:
\once\override Score.Rest #'extra-offset = #'(.3 . -4.1)
<<{r8 [ c8\rest ]}\\{4 }>> |
But if there are many rest-shifings like this, the \rest coding is to
prefer, because of the shifting with \override Score.Rest is relative
to
the given note\rest, otherwise the rest's vertical position is
orientated to the note before, and it would be too complicated to set
each different numbers of shifting.
I think, this will help You. :)
Best Regards Roland
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Can'T compile lily 2.2.0
Hello all, trying to compile lily 2.2.0 I get the following error:
make[1]: Wechsel in das Verzeichnis Verzeichnis
»/home/jankoh/lilypond-2.2.0/mf«
mftrace -I ./out/ --pfa --simplify --keep-trying cmbxti8 && mv
cmbxti8.pfa ./out/
mftrace 1.0.31
Font `cmbxti8'...
error: can't find file `f7b6d320.enc'
Traceback (most recent call last):
File "/usr/local/bin/mftrace", line 1134, in ?
error (_("can't find file `%s'" % codingfile))
File "/usr/local/bin/mftrace", line 134, in error
raise _ ("Exiting ... ")
Exiting ...
make[1]: *** [out/cmbxti8.pfa] Fehler 1
make[1]: Verlassen des Verzeichnisses Verzeichnis
»/home/jankoh/lilypond-2.2.0/mf«
make: *** [all] Fehler 2
kohni:/home/jankoh/lilypond-2.2.0 #
I tried to google but without suggestion. Can you help me find the error?
Thanks in advance!
Regards Jan
--
OpenPGP public key available:
http://home.arcor.de/jan.kohnert/gnupg_publickey.asc
Key-Fingerprint:
BA8E 11D1 FE7C 9353 7276 5375 486E 9BED 2B03 DF29
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
