On Thu, 2017-03-16 at 22:32 +0000, Burton, Ross wrote: > If I do a build with rm_work enabled I tend to get this error at > rootfs time: > > > ERROR: core-image-sato-1.0-r0 do_image_wic: Error executing a python > function in exec_python_func() autogenerated: .... > Exception: FileExistsError: [Errno 17] File exists: > '/data/poky-master/tmp/sysroots-components/corei7-64/glibc/usr/lib/crt1.o' -> > '/data/poky-master/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/recipe-sysroot/usr/lib/crt1.o' > > > ERROR: core-image-sato-1.0-r0 do_image_wic: Function failed: > extend_recipe_sysroot > ERROR: Logfile of failure stored > in: > /data/poky-master/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/temp/log.do_image_wic.21552 > ERROR: Task > (/home/ross/Yocto/poky/meta/recipes-sato/images/core-image-sato.bb:do_image_wic) > failed with exit code '1' > > > Reverting this patch makes it go away.
I think I have seen that before, but not necessarily (not sure anymore) in the context of rm_work. If I remember correctly, these were really two different crt1.o files, one from glibc, the other from glibc-initial. I couldn't reproduce it at that time. I'll check whether I can trigger it now. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core