Re: Build error regarding mf2pt1 with latest texlive (2011) and lilypond 2.14.1

[Werner LEMBERG]

>> What exactly is the `latest texlive'?
>
> I may be able to test TeXLive from SVN to see if the problem
> persists.

It persists, and it is the same problem as with the Arch distribution:
mpost no longer dumps a .mem file but reads the corresponding .mp file
directly.

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.

> Now I'm curious about the "texlive-workaround" patch(es) that Arch
> uses and if they're relevant here.  The stable LilyPond 2.14.1 is
> built using the patch shown here:
> http://projects.archlinux.org/svntogit/community.git/tree/lilypond/repos/community-x86_64/texlive-workaround.patch

This patch is a temporary one, I believe, which corrects a problem
with a previous version of the TeXLive SVN which Joe Neeman has
reported (cf. http://comments.gmane.org/gmane.comp.tex.metapost/1806),
but this has been fixed meanwhile so the patch is no longer necessary.

> Also, there is a "lilypond-git" build script that uses a new patch
> to address the problem I reported.  Please see
> http://aur.archlinux.org/packages.php?ID=17366 for more details.

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.


    Werner