On Thu, Oct 18, 2012 at 12:25:05PM -0700, Saul Wold wrote: > Present the manifest file that contains the matches for > files being installed to a location that already contains > that file. This will help to determine which is the correct > recipe to fix when this occurs. > > [YOCTO #3191]
Can we do the same when removing files from sysroot? To catch errors like this: http://git.openembedded.org/openembedded-core/commit/?id=6b12d4cd39bacb087654b59e25f5052a4e839b26 12:40:15 < JaMa> it depends on order of tasks 12:41:27 < JaMa> gettext-native depends on gettext-minimal-native, so gettext-minimal-native installs own config.rpath to sysroot (when gettext-native "owns" it too) 12:41:55 < JaMa> then gettext-native is built and before populting sysroot it removes own files there (including config.rpath) 12:43:45 < JaMa> and because sstate assumes that every file in sysroot is provided by exactly one recipe, gettext-minimal-native looses his config.rpath 12:44:49 < JaMa> now there is at least warning when 2 recipes are installing the same file to sysroot, but that doesn't resolve this issues when some file is "moved" between recipes 12:47:30 < JaMa> because gettext-minimal-native is only recipe installing it 12:47:39 < JaMa> and gettext-native is only removing it If we check manifests from other recipes before removing files we can show warning that gettext-native is trying to remove config.rpath now provided by gettext-minimal-native and keep config.rpath in sysroot. Now everybody doing incremental builds needs to call bitbake -c cleansstate gettext-minimal-native Cheers, -- Martin 'JaMa' Jansa jabber: [email protected]
signature.asc
Description: Digital signature
_______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
