Dear friends,
after a long time I'm trying lilypond again...
Running ./configure and `make; make install' was fine.
But trying `make -C Documentation/user dvi' gives *a lot* of problems.
All details can be found in the first attached log file.
. I had to make a link from my <texmf>/.../tfm/public/cm directory to
lilypond-1.3.61/tfm, otherwise lilypond doesn't find the metric
files.
. The files 794666487.ly, 1308576182.ly, 1516850187.ly, 1672380157.ly,
1889151134.ly produce
programming error: Infinity or NaN encountered
while outputting the TeX file.
. The call to 1604370556.ly caused
Error command exited with value 7
which is not very helpful...
I assume this means `memory exhausted' or something else, since my
computer was swapping and swapping and swapping (I have 64MByte main
memory).
Is it possible that there is a problem with memory-deallocation if
lilypond is called with more than one input file? It seems that the
processing of file 1604370556.ly exactly hits the acceptable limit
on my computer -- before that file, I haven't had the feeling that
my laptop was slower due to swapping.
. lilypond looks for the non-CM font `cmti5' which is part of the
Sauter extensions. I strongly suggest to add kpathsea support so
that such missing fonts can be generated *and found* automatically.
. Why are PNG images created for the make target `dvi'? This is
really unnecessary.
OK, I've restarted `make', and I get the final problem:
error: incorrect mudela version: 1.3.56 (1.3.59, 1.3.61)
Error command exited with value 256
It seems that the version number hasn't been updated correctly.
Details can be found in the second attached log file...
Some other suggestions:
. I think that an error message should always start a new line. Some
other log messages should also start a new line -- the longest line
I've encountered while logging the above make call has
1387 characters. This is really uncomfortable IMHO.
. If a warning or error happens please always emit the affected file
(or, if possible, the affected line). Especially if lilypond is
called with multiple files this is very helpful.
. What about adding a switch to reduce the verbosity of messages? I
can imagine that most users are usually not interested in seeing the
inclusion process of the start-up files.
. There is a typo somewhere in the mf files:
parantheses -> parentheses.
make.documentation.log.bz2
make.documentation.log1.bz2
