Re: broken clef glyph

[David Kastrup]

Cc Norbert Preining since he's my best guess about who would have an
idea how to proceed here.

Han-Wen Nienhuys <address@hidden> writes:

> Hi there,
>
> my clef glyph looks broken (see attachment).

Permalink at
<URL:http://permalink.gmane.org/gmane.comp.gnu.lilypond.bugs/38148>

See also
<URL:http://lists.gnu.org/archive/html/lilypond-devel/2013-09/msg00000.html>

> I am on
>
> * commit 3c6b011ceedc9f3eb7908acac19cf7fe7bf54f5c (from Aug 25)
>
> * Fedora 19, which has MetaPost 1.802 (TeX Live 2013), on x86_64
>
> anyone ideas where to find the cause?

sudo tlmgr update --all

or if you have TeXlive not in the system path

sudo `which tlmgr` update --all

The question is how to deal with that reasonably well.  Ubuntu 13.10
alpha has the same problem, most likely inheriting from Debian
(testing?) which probably has taken the broken version from the official
TeXlive2013 DVD, or has its own broken compiled version.  I have seen
this problem first with the i386 (or i686?) version of Ubuntu 13.10
alpha.

Now Fedora as well.  Presumably both Debian and Fedora recompile from
source with some version of GCC, so the problem may well be more than
"just" a compiler bug in a single GCC version (reportedly, the version
on TeXlive2013 has fixed the binaries by recompiling with a different
GCC version).

If this bug of TeXlive will persist into stable GNU/Linux distributions,
it will likely have a devastating effect on LilyPond's reputation.  It's
not just the clef glyph that is prominently broken, but also a number of
other frequent glyphs like the flags.

-- 
David Kastrup