On 6/30/2019 5:54 PM, [email protected] wrote: >> /update_pixbuf_cache: cannot create >> /home//riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core- >> image-full-cmdline/1.0-r0/rootfs/usr/lib/gdk-pixbuf- >> 2.0/2.10.0/loaders/../loaders.cache: >> Directory nonexistent" > Knowing which branches (sumo vs. thud) and which layers does help put a > different perspective on this issue and helps us help you! >
Sorry, I thought I mentioned this before. Issue showed up in thud. It was not there on sumo. > Is this a difference in dash shell vs bash shell (e.g. for /bin/sh) on > these machines? (if I had to guess that is where I'd start) Dash vs. bash didn't make a difference. I changed build machine to have /bin/sh point to /bin/bash rather than /bin/dash. The commit on github also says "it may help" with the postinst. Apparently, the issue has been solved mysteriously for them. One thing that issue on github mentions is that these issues were being ignored in sumo but are marked as real failures starting from thud. -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
