On Mon, 11 Nov 2019, at 14:49, Mike Looijmans wrote: > Starting with warrior build, I'm getting build fails due to "File name too > long" in sstate-cache filenames. This is probably related to having long > names > for machines, but this did not happen in previous releases. For example: > > OSError: [Errno 36] File name too long: > '/mnt/.../sstate-cache/52/sigtask.9u_r4yv2' -> > '/mnt/.../sstate-cache/52/sstate:u-boot-xlnx:topic_miamilite_florida_test_xc7z010-oe-linux-gnueabi:v2019.01-xilinx-v2019.1+gitAUTOINC+d895ac5e94:r0:topic_miamilite_florida_test_xc7z010:3:52cb29cef3922da53a752f38e9bbfdef878af51813dc095d9c1451d572844f93_prepare_recipe_sysroot.tgz.siginfo' > > > What can I do about this? There's no hint in the error message and searching > for the message text doesn't show much except issues with crypto filesystems, > which doesn't apply. The filesystem is just plain ext4.
This looks like https://bugzilla.yoctoproject.org/show_bug.cgi?id=13177 which I filed earlier this year. I haven't found a solution which is acceptable to everyone though and since then I've rarely if ever actually hit this problem. -- Paul Barker Managing Director & Principal Engineer Beta Five Ltd -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
