Re: Compilation error, due to changes in pango

I don't know if this has been reported, but I just updated pango on Arch, and the version 1:1.44.5-1 is working fine now ! -- Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html ___ bug-lilypond mailing list bug-lilypond@gnu.org https://

Re: Compilation error, due to changes in pango

On Tue, Aug 06, 2019 at 12:11:44PM +0200, Knut Petersen wrote: > On 04.08.19 13:39, Werner LEMBERG wrote: > >>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.

Re: Compilation error, due to changes in pango

On 04.08.19 13:39, Werner LEMBERG wrote: 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. Let's hope t

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

Re: Compilation error, due to changes in pango

Hello, also on Arch Linux. 1.44-1 lists lrwxrwxrwx root/root 0 2019-07-27 22:40 usr/lib/libpango-1.0.so -> libpango-1.0.so.0 lrwxrwxrwx root/root 0 2019-07-27 22:40 usr/lib/libpango-1.0.so.0 -> libpango-1.0.so.0.4400.0 -rwxr-xr-x root/root313016 2019-07-27 22:40 usr/lib/libpa

Re: Compilation error, due to changes in pango

Werner LEMBERG wrote > Can you please tell me the librarie's .so numbers of 1.43.0 and 1.44.1 > (or 1.44.2)? > > > Werner Yes sure, but I don't know how to find that... -- Sent from: http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html ___ b

Re: Compilation error, due to changes in pango

> For info, I'm using Archlinux and after making a maintenance update > via pacman, I had a similar problem. LilyPond became almost > unusable with pango 1.44.1-1 and I was forced to downgrade to > 1.43.0.-2. Can you please tell me the librarie's .so numbers of 1.43.0 and 1.44.1 (or 1.44.2)?

Re: Compilation error, due to changes in pango

Hi all, For info, I'm using Archlinux and after making a maintenance update via pacman, I had a similar problem. LilyPond became almost unusable with pango 1.44.1-1 and I was forced to downgrade to 1.43.0.-2. Everything worked normally again after that. I'll stick with that for now but I hope a so

Re: Compilation error, due to changes in pango

Thanks for reporting, this has been entered as https://sourceforge.net/p/testlilyissues/issues/5545/ I hope the ‘maintainability’ label is appropriate. Best, Simon On 30.07.19 21:18, t.sefzick wrote: With the new pango version 1.44 compilation of src/lilypond/lily/pango-font.cc gives warnin

Re: Compilation error, due to changes in pango

Indeed, Pango 1.44 dropped support to FreeType font, as posted in https://blogs.gnome.org/mclasen/2019/05/25/pango-future-directions/ Em ter, 30 de jul de 2019 às 16:18, t.sefzick escreveu: > > With the new pango version 1.44 compilation of > > src/lilypond/lily/pango-font.cc > > gives warnings a

Compilation error, due to changes in pango

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'