[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lilypond book still don't print beams and slurs / SuSE 7.1
From: |
Olivier Guéry |
Subject: |
Re: lilypond book still don't print beams and slurs / SuSE 7.1 |
Date: |
Thu, 29 Mar 2001 03:07:02 +0200 |
Hello,
I send back my own message beacause I find a strange thing :
For the following problem I used the "ln -s
/usr/local/share/lilypond/mf
lilypond" (before I use it I had no problem, but it was on a Mandrake and now
I'm under SuSE).
I tried to remove the link, reinstall lily (1.3.144) and tring to unse
lilypond, here is the oiutput :
kpathsea: Running mktexmf feta16
! I can't find file `feta16'.
<*> ...:=ljfour; mag:=1; nonstopmode; input feta16
Please type another input file name
! Emergency stop.
<*> ...:=ljfour; mag:=1; nonstopmode; input feta16
Transcript written on mfput.log.
mktextfm: `mf \mode:=ljfour; mag:=1; nonstopmode; input feta16' failed.
kpathsea: Appending font creation commands to missfont.log.
! Font \magfontSFHRomMMBo=feta16 not loadable: Metric (TFM) file not found.
l.302 ...font\magfontSFHRomMMBo=feta16 scaled 1000
?
kpathsea: Running mktextfm feta-nummer8
mktextfm: Running mf \mode:=ljfour; mag:=1; nonstopmode; input feta-nummer8
This is METAFONT, Version 2.7182 (Web2C 7.3.1)
kpathsea: Running mktexmf feta-nummer8
! I can't find file `feta-nummer8'.
<*> ...ur; mag:=1; nonstopmode; input feta-nummer8
Please type another input file name
! Emergency stop.
<*> ...ur; mag:=1; nonstopmode; input feta-nummer8
Transcript written on mfput.log.
mktextfm: `mf \mode:=ljfour; mag:=1; nonstopmode; input feta-nummer8' failed.
! Font \magfontUIMRomMMBo=feta-nummer8 not loadable: Metric (TFM) file not
foun
d.
l.303 ...agfontUIMRomMMBo=feta-nummer8 scaled 1000
? )
Overfull \vbox (2.49998pt too high) has occurred while \output is active
[4]
Overfull \vbox (2.49998pt too high) has occurred while \output is active
[5]
Overfull \vbox (2.49998pt too high) has occurred while \output is active
[6]
No file Castor.bbl.
Overfull \vbox (2.49998pt too high) has occurred while \output is active
[7] <qa_barrage1.ps> <qa_barrage2.ps> <qa_barrage3.ps>
Overfull \vbox (2.49998pt too high) has occurred while \output is active
[8] <qa_barrage_voutes.ps> <qa_barrage_contreforts.ps>
Overfull \vbox (2.49998pt too high) has occurred while \output is active
[9]
Overfull \vbox (2.49998pt too high) has occurred while \output is active
[10] (Castor.aux) )
Output written on Castor.dvi (10 pages, 38188 bytes).
Transcript written on Castor.log.
And the . dvi file had no tie, slur; and no note head.
If I put the link back, I get the same problem as last message... I
don't
understand anything on fonts... But it seems that there's a problem.
I read all the message about the SUSE 7.1 problems, but I don't
understan
What I must do in fine :o)
Anyone with the same distrubution can test my file ? PLease, it's just
a
joke but it's for a friend birthday and I'm 5 days late...
Thank's for all,
nemo.
> > Hello,
> I tried, has Matt said me to set the TEXINPUTS variable to the corect
> path
> but it won't works.
> The strange thing :
> "lilypond-book toto.tex" produce a lily-*.ly a lily-*.tex and a
> toto.latex files.
> Running ly2dvi on the .ly file produce the good .dvi output.
> Running tex on the .tex file produce the good .dvi output.
> Running latex on toto.latex produce a .dvi with no beams and no slur (I
> dont test other features).
> I have no warnig during lilypond-book or latex (exept overfull \vbox...
> as
> usual :o).
> So what's the problem. I have no problem to built the documentation with
> all the beam/slurs.
> Is anybody have the same problem ? I send the .tex source code (for the
> french readers it's a joke/fake report on beaver... and not yet finish).
> Thanks for all,
> nemo.
--
Olivier Guéry address@hidden
Castor.tex
Description: Text Data