As far as I skimmed the discussions of the last days, this didn't show up yet:

In my LilyPond module I call the programm like so:

\def\LP{mtxrun --ifchanged="\lily!filename.tmp" --exec bin:lilypond - dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts -ddelete- intermediate-files "\lily!filename.tmp"} \def\PDF{texmfstart --ifchanged="\lily!filename.eps" pstopdf "\lily! filename.eps"}

\executesystemcommand{\LP}
\executesystemcommand{\PDF}

The former definition results in this call:

mtxrun --ifchanged="c_whatshallwedo-lilypond-1.tmp" --exec bin:lilypond -dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts - ddelete-intermediate-files "c_whatshallwedo-lilypond-1.tmp"

The .tmp file exists and contains the right LilyPond code.
But I get an error like this from the LP call:

############################################################
.../texmf/tex/texmf-osx-intel/bin/mtxrun:1953: attempt to call field 'HEXsum' (a nil value)
############################################################

Line 1953 is:

return md5.HEXsum(data)

Looks like a bug in mtxrun to me - or in Lua's md5 module.

http://www.keplerproject.org/md5/manual.html#lua_api says, there'd be only "sum" and "sumhexa" methods. Replacing "HEXsum" with "sum" works, "sumhexa" gives the same error as above.


The PDF call gives:

MTXrun | file 'c_whatshallwedo-lilypond-1.eps' is unchanged

Even if the .eps file doesn't exist at all.


There are no .md5 files like before. I guess that's right?


Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to