Upstream has rolled back this change. I'm sure it will take a littleb bit of
time to land in distros, but when it does Lilypond compiled agoinst 1.43 should
work again even with new Pango dropped in. What that won't solve is being able
to compile against 1.44, which is also a problem because distros that have new
Pango won't be able to update (and hence include) Lilypond.
This is already an issue on Arch that is stuck one point release behind because
it won't compile. As soon as this compile time issue is fixed it should make
it's way to a point release so Arch and other up to date distros can keep using
it on new systems.
---
** [issues:#5545] Compatibility with pango 1.44**
**Status:** Accepted
**Created:** Wed Jul 31, 2019 07:59 AM UTC by Simon Albrecht
**Last Updated:** Wed Aug 07, 2019 05:16 AM UTC
**Owner:** nobody
[Reported by T.
Sefzick:](https://lists.gnu.org/archive/html/bug-lilypond/2019-07/msg00035.html)
With the new pango version 1.44 compilation of
`src/lilypond/lily/pango-font.cc`
gives warnings about
`'void* pango_fc_font_lock_face(PangoFcFont*)'`
to be deprecated and
`'pango_font_get_hb_font'`
should be used instead.
followed by
`error: invalid conversion from 'gpointer' {aka 'void*'} to 'FT_Face' {aka
'FT_FaceRec_*'}`
Seems that pango doesn't work with freetype fonts anymore.
A side note: lilypond executables compiled with pango <=1.43
produce an empty 1st page when run with pango 1.44 installed.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list._______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
