Re: Compilation error, due to changes in pango

> In my case, it's not really a compilation error but mostly strange > behavior with texts and markups. Here is a very small example with > a bug in the appearance of the TimeSignature. > > Hmm. The only thing you did is installing a n

Re: Compilation error, due to changes in pango

Werner LEMBERG wrote > The question is now what exactly causes this: > > error: invalid conversion from 'gpointer' {aka 'void*'} > to 'FT_Face' {aka 'FT_FaceRec_*'} > > during the lilypond compilation? Is this really caused by pango? Or > is this a glib issue? Could you investigate?

Re: Compilation error, due to changes in pango

> The question is now what exactly causes this: > > error: invalid conversion from 'gpointer' {aka 'void*'} > to 'FT_Face' {aka 'FT_FaceRec_*'} > > during the lilypond compilation? Is this really caused by pango? Or > is this a glib issue? Could you investigate? Pango 1.44 seems to

Re: Compilation error, due to changes in pango

> 1.44-1 lists > > libpango-1.0.so.0.4400.0 > > 1.44-2 lists > > libpango-1.0.so.0.4400.2 > > 1.43.0 lists > > libpango-1.0.so.0.4300.0 Thanks! So the removal of Type 1 and bitmap support in Pango didn't cause an increase of the dynamic library's major version (i.e., the first zero after