Murray Adelman writes:
|
| I now have installed lilypond 0.1.77. There seems to be a
| problem with the texinfo files produced: Here is part of the
| error message:
|
|makeinfo -o out/lilypond.info out/topinfo.texinfo
|Making info file `out/lilypond.info' from `out/topinfo.texinfo'.
|./man/out/convert-mudela.texinfo:67: Unknown info command `url'.
|./man/out/convert-mudela.texinfo:67: Misplaced `{'.
|./man/out/convert-mudela.texinfo:67: Misplaced `}'.
Murray,
Don't know about this, but when I checked 0.1.77 lilypond.info it did
have \input texinfo at every place a included file might be. Version
0.1.80 showed the same thing. (Something is broken)
| I installed it anyway. mi2mu crashes on me and dumps core. I
| did compile with debugging and checking enabled, so the core
| file should have some information. I will be glad to try to
| examine it if given specific instructions. All I know about
| gdb is how to call it.
|
| Here are the error messages that come with the "crash":
A 30 second gdb lesson
o execution
% gdb executable [core]
o if you load the optional core gdb will start up with a stack dump
telling you where the programmed cored
o help
help (follow displayed instructions)
o break points
b function-name
b line-number
b filename:line-number (Not 100% sure on this one)
o movement
r args (run program with args)
n (execute next line)
s (step into next line)
o print
p variable-name
Not much, but better than a blank as my sister-in-law always says.
| To tell the truth, I couldn't get mi2mu to work on any of the
| MIDI files I have laying around on my filesystem. Here is the
| error message from one of the less fatal MIDI files:
|
|eppes:/usr1/src/lilypond-0.1.75/TESTING# mi2mu example.mid
|mi2mu FIXME /FlowerLib 1.1.44. of Jul 19 1998 17:34:25
|Parsing...
|[1][683]error: ugh
I get similar result with pl 77 and pl 80 with a midi file lilypond
created... Curious. Murray I have not experienced a core as of yet.
|The file GREENGRO.mid was taken from some site that offers public domain
|MIDI files. The file example.mid comes with the midi2tex program.
|
|There is a chance I haven't mastered the program yet.
|
|To pick a nit:
|
| The "-d" option seems to be removed from mi2mu but not from
| the documentation. The error report is strange. I think
| some variables have not been expanded. Here is what using the
| option yields:
|
|eppes:/usr1/src/lilypond-0.1.77/TESTING# mi2mu -d example.mid
|mi2mu: unrecognized option: `ption: `%s''
|
| On the other hand "--debug" does work.
Same experience here except my -d error message is better than yours:
mi2mu: unrecognized option: `Got 2
n âÇ'
Looks like we got some work to do.
Jeff
--
Jeffrey B. Reed
[EMAIL PROTECTED]
