There has been a problem that has been around for years and years, in fact, as long as the 'pango' project has existed.
Compiling in T2, pango failed with this: ------------------------------------------ 00:21:43 =[5]=> Building gnome2/pango [1.32.5 9.0-trunk]. -> Parallel build using 4 jobs enabled. -> Reading package config: package/gnome2/pango/pango.conf -> Preparing build in src.pango.wary6.20130704.002134.3001.puppypc24301 -> Building. Writing output to $root/var/adm/logs/5-pango.out !> checking for CoreText availability... no !> checking for CAIRO... yes !> checking which cairo font backends could be used... none !> configure: Disabling cairo support !> configure: error: *** Could not enable any backends. !> *** Must have at least one backend to build Pango. ------------------------------------------------- If you google about this, you will find heaps of others have hit this problem. The solution is that 'fontconfig' must be updated to the latest version. I have done this in t2, grabbed fontconfig 2.10.2, pango is then happy. Unfortunately, although this problem has been reported ad-nauseum, the pango developers have never incorporated a check into their configure to advise upgrading fontconfig. Anyway, that is the fix. I guess, whenever you upgrade pango, make a mental note to also update fontconfig. Oh, note, the fontconfig patch 'default-fontpath.patch' doesn't work anymore, so I removed it. Regards, Barry Kauler ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
