(Note: this message is in reply to an existing thread. I just subscribed to the ML. I apologize if this creates a new thread.)
Thank you for clarifying the problem surrounding mpost. > Attached is a fix which makes it work again in lilypond (without > breaking backwards compatibility to older mpost versions), and which > I've applied to the git repository. Please test and report whether it > works so that we can mark the bug as fixed. Tested tonight, without the texlive workaround patches. Works perfectly. :) > Note that the mf2pt1 script itself is *not* broken! If you use it as > originally intended, it makes no difference whether mpost creates a > .mem file or not. For security reasons, however, lilypond executes > everying within a temporary subdirectory so that the mf2pt1.mp file > was no longer visible to mpost. Yes, I finally understand this. :) My hack on mf2pt1.pl was merely a workaround to make the build work for me since I didn't know about the mpost issues initially, or how to correct them. It wasn't my intention to imply that the script was broken. Thanks for your work! Marc _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
