well ive been working on a pango and gtk2 ipk for a few days and came across something worth mentioning, thoughi feel a "solution" is not necessary...
during compilation and build (native) of pango and gtk2 it mentions a warning during both of the same nature... for now ill jsut use pango as the example:
that it could not generate pango.modules and that it should be created later with pango-querymodules, no problem. so i run pango-querymodules > /usr/local/etc/pango/pango.modules and the garbled app font becomes readable
apon inspection of an example pango ipk (from the beta1 pdaxrom feed), i noticed this was done via postinst...
so initially i set out to have the above command issued by 'postint' script of ipkg install, but i ran into problems that when postinst is run the symlinks havent been created yet, so i doesnt find any modules and you end up with an empty pango.modules file...
i spent a bit of time mucking around with it as i thought it might be important to have it generated "dynamically" as such after an ipkg install to detect a setup/system specific module installation configuration, but alas not luck...
so i just grabbed the pango.modules file i generated after ipkg finished everything, and packaged it back into the ipk, whilst removing the postinst script... now it all works ok...
i imagine there could possibly be an issue with it not having mention of a particular module you may have installed
but this could be fixed by that person by re-running the query.
during my look around i noticed there are some extras you can pass to pango-querymodules, ala:
The Pango module path is specified by the key Pango/ModulesPath in the Pango config database, which is read from sysconfdir/pango/pangorc, ~/.pangorc and the file specified in the environment variable PANGO_RC_FILE.
but i idnt really figure this could be of much use...
