On Fri, Jan 13, 2012 at 3:45 PM, Khem Raj <[email protected]> wrote: > On Fri, Jan 13, 2012 at 1:37 AM, Carmelo AMOROSO <[email protected]> > wrote: >>> and since I see the same issue on all architectures probably its not >>> elfinterp changes >>> too. Mostly it seems likely that it could be in the way the scopes are >>> being handled >>> >> >> we have reviewed several times this change before committing. Anyway we >> will review it again. We have not ever seen any failure in the lookup >> with all of our tests. The only change in the way the symbol scope is >> created is in where the ld.so is added. >> In the original code it was the last entry of the global scope, while >> with the new structure in place it was added as soon as found (as glibc >> actually does).... and I don't really think this could have some impact. > > I tried to reverse it as well but the problem remained. > >> >> We are trying to startup a X system on our platform. Is there any simple >> X app we can run to show the failure ? >> >> Is some .so failing to be dl-opened due to unresolved symbol ? > > this is potentially possible. I will try to debug it through
This is the problem that happens with the new scoping and does not happen without it Error reading Pango modules file (matchbox-desktop:1058): Pango-CRITICAL **: No modules found: No builtin or dynamically loaded modules were found. PangoFc will not work correctly. This probably means there was an error in the creation of: '/etc/pango/pango.modules' You should create this file by running: pango-querymodules > '/etc/pango/pango.modules' (matchbox-desktop:1058): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='latin' (matchbox-desktop:1058): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='common' _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
