Graeme Gregory wrote: >>> Since today i see a similar problem when doing a clean bitbake of >>> glib-2.0. It seems to be a problem with automake/automake. :( >> >> I think i've identified this patch as cause of the problems. >> >> commit b1caa21ab2590689f3b6ff68483803701c12d721 >> Author: Graeme Gregory <[email protected]> >> Date: Tue Jan 26 12:02:08 2010 +0000 >> > Guys there is zero point sending me emails direct if you dont actually > tell me any information.
Sorry about that. But i wasn't sure if you read the ml daily. So i put you on the Cc. BTW, i would call the hint, that your commit broke[1] the baking of at least glib-2.0 (which isn't that exotic) an 'information'. [1] I've rechecked this again with angstrom distro and hipox, beagleboard, and x86 machine making a clean build of glib-2.0: rm -rf tmp.5 bitbake glib-2.0 Steffen _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
