pango +quartz: cairo backend is unusable

[com-macosforge@…]

% sw_vers 
ProductName:	Mac OS X
ProductVersion:	10.6.8
BuildVersion:	10K549
% port installed | egrep 'pango|cairo'
  cairo @1.12.2_1+no_x11+quartz (active)
  pango @1.30.1_2+no_x11+quartz (active)
% pango-view --backend=ft2 -q -o text.png -t 'Hi there!'                   
% pango-view --backend=cairo -q -o text.png -t 'Hi there!'       
**
Pango:ERROR:pangocoretext.c:49:pango_core_text_font_finalize: assertion failed: (priv->fontmap != NULL)
[1]    81474 abort      pango-view --backend=cairo -q -o text.png -t 'Hi there!'

My guess is the Core Text support wasn't tested upstream (or perhaps only on 10.7?), but I haven't investigated further. Perhaps MacPorts can build without the cairo backend?

[com-macosforge@…]

To be clear, this is specific to +quartz; it works fine with +x11.

[mf2k (Frank Schima)]

In the future, please Cc the port maintainer(s).

[ryandesign (Ryan Carsten Schmidt)]

Could you please test whether the pango-devel port fixes this? You'll need the glib2-devel port as well.

[com-macosforge@…]

No, it doesn't fix the problem. I previously had an older version of pango installed which didn't have this problem.

Incidentally, looks like gtk-doc (and its 5000 dependencies) are required to build pango-devel too.

[ryandesign (Ryan Carsten Schmidt)]

Replying to com-macosforge@…:

No, it doesn't fix the problem. I previously had an older version of pango installed which didn't have this problem.

Ok, thanks for testing that. I recommend you file a bug report about the problem in ​their issue tracker then, or write to ​their mailing list about it. I doubt the problem is specific to MacPorts. cairo is pretty much the backend that programs using pango will expect to always be available; I anticipate that trying to disable it would break a lot more ports.

Incidentally, looks like gtk-doc (and its 5000 dependencies) are required to build pango-devel too.

Thanks for noticing that; that wasn't intentional. Fixed in r97589.

[ryandesign (Ryan Carsten Schmidt)]

Did you report this problem to the developers? What did they say? Is it still a problem with 1.32.5 to which the pango port was just updated?

[ryandesign (Ryan Carsten Schmidt)]

I'm not able to reproduce this issue with cairo @1.14.0_0+quartz+universal+x11 and pango @1.36.8_1+quartz+universal+x11.

[com-macosforge@…]

I never got around to reporting this, but it is no longer a problem as of 10.10 with current cairo/pango port versions, even without x11 (which was my original concern).

Thanks for checking into it again.