On Sun, Sep 25, 2016 at 1:53 PM, Masamichi Hosoda <truer...@trueroad.jp> wrote:
> >>> https://bugs.freedesktop.org/show_bug.cgi?id=97546 > >>> > >>> The proposed fix hasn't been applied yet to the fontconfig git > >>> repository – maybe we should downgrade GUB's fontconfig version to > >>> 2.12.0 until this is fixed. > >> > >> I think that there is another possible solution. To use the > >> proposed patch in GUB. > > > > Certainly. However, I can't estimate whether there aren't side > > effects... On the other hand, given that the patch is from the > > fontconfig maintainer, there are high chances that it is the right > > one :-) > > I've created pull request for GUB. > https://github.com/gperciva/gub/pull/29 > > The patch is only applied to building binary for mac. This is really great to see. And accords exactly with the test results I added to the original thread showing that 2.19.47 (and .48) are, in fact, definitely rebuilding one of the font caches at every run of LilyPond. Thanks very much for tracking this down! -- Trevor Bača www.trevorbaca.com soundcloud.com/trevorbaca _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
