On Wed, 2003-07-23 at 11:46, Han-Wen Nienhuys wrote:
> 
> the correct font build log should start with
> 
>       (feta20.mf (feta-autometric.mf
>               ******************************************************
>       Using feta Autometric macros. 
>       Do not worry about the @ signs in the output, they are not errors. 
>       ******************************************************)
>       @{font@:GNU@:LilyPond@:feta@:[EMAIL PROTECTED]
>       (feta-generic.mf (feta-macros.mf) (feta-params.mf) (feta-eindelijk.mf
>       @{group@:[EMAIL PROTECTED]
>       @{char@:whole rest@:33@:0@:7.5@:3.125@:0@:0@:[EMAIL PROTECTED] [33]
>                             ^^
> 
> note that it should start with 33. 


Here is the beginning when I run lilypond-book:

(/usr/share/texmf/tex/latex/lilypond/feta20.tex)kpathsea: Running
mktextfm  feta16
mktextfm: Running mf \mode:=ljfour; mag:=1; nonstopmode; input feta16
This is METAFONT, Version 2.7182 (Web2C 7.3.1)
 
(/usr/share/texmf/fonts/source/lilypond/feta16.mf
(/usr/share/texmf/fonts/source/lilypond/feta-autometric.mf
******************************************************
Using feta Autometric macros.
Do not worry about the @ signs in the output, they are not errors.
******************************************************)
@{font@:GNU@:LilyPond@:feta@:[EMAIL PROTECTED]
(/usr/share/texmf/fonts/source/lilypond/feta-generic.mf
(/usr/share/texmf/fonts/source/lilypond/feta-macros.mf)
(/usr/share/texmf/fonts/source/lilypond/feta-params.mf)
(/usr/share/texmf/fonts/source/lilypond/feta-eindelijk.mf
@{group@:[EMAIL PROTECTED]
@{char@:whole rest@:0@:0@:6@:2.5@:0@:0@:[EMAIL PROTECTED] [0]
@{char@:half rest@:1@:0@:6@:0@:2.5@:1@:[EMAIL PROTECTED] [1]
@{char@:whole rest (outside
staff)@:2@:0@:6@:2.5@:0.40002@:0o@:outsidewholerest
@} [2]

It is *not* starting with 33.  What now?



> > M lilypond/buildscripts/clean-fonts.sh
> > 
> > I don't know what the 'M' means.  I mention it because it may be a clue
> > (or not).
> 
> it means you have editted it locally.

Ah, I see.  I did edit it.  I changed @SHELL@ to /bin/sh so it would
work.  Is that the correct procedure?  If not, is this part of the
trouble I'm having?

-David



_______________________________________________
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to