On Sat, 2015-03-21 at 03:11 +0100, Martin Jansa wrote: > On Mon, Mar 16, 2015 at 05:42:36PM +0000, [email protected] wrote: > > Module: openembedded-core.git > > Branch: master > > Commit: f0e3db4eaacc32423934ce09b91bc619dc5dbd21 > > URL: > > http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=f0e3db4eaacc32423934ce09b91bc619dc5dbd21 > > > > Author: Jonathan Liu <[email protected]> > > Date: Mon Mar 9 12:13:56 2015 +1100 > > > > fontcache.bbclass: prepend to PACKAGEFUNCS instead of appending > > > > Appending to PACKAGEFUNCS results in the font packages missing the > > postinst/postrm scripts and the fontconfig cache not being generated > > in /var/cache/fontconfig when creating images or installing font > > packages. This is because the package data has already been emitted > > by emit_pkgdata in PACKAGEFUNCS. Prepend to PACKAGEFUNCS to ensure > > add_fontcache_postinsts is executed before emit_pkgdata. > > It's not caused by this change, but fixing this issue revealed that > fc-cache doesn't really work here. > > Every time the intercept_scripts/update_font_cache executes qemu it gets > "stuck" eating a lot of cpu and memory until it dies. Is anyone alse > seeing this behavior? > > WARNING: The postinstall intercept hook 'update_font_cache' failed (exit > code: 137)! See log for details! > WARNING: The postinstalls for the following packages will be postponed for > first boot: liberation-fonts > ERROR: The following packages could not be configured offline and rootfs is > read-only: ['liberation-fonts'] > ERROR: Function failed: do_rootfs > > bitbake 32618 98.8 67.1 11031512 10983420 pts/3 R+ 03:00 4:53 > qemu-i386 -r 2.6.32 -L /OE/rootfs -E > uD_LIBRARY_PATH=/OE/rootfs//usr/lib:/OE/rootfs//lib > /OE/rootfs/usr/bin/fc-cache --sysroot=/OE/rootfs
There are a couple of bugs in the bugzilla around this. One seemed to be related to circular symlinks in udev's ptest package which was supposedly fixed. The other claims to have been resolved by upgrading fontconfig to a version which doesn't have issues with circular paths. There is general confusion about how to reproduce the issue and what the real problem is though. Does your system have any recursive directory structures? I'd like to get to the bottom of the issue and fix it once and for all but we likely need more info. Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
