Re: [OE-core] Troubleshooting sstate cache

2018-08-28 Thread Nick Winters
The problem may be a result of executables being built with absolute paths to their shared libraries. When I do the following: ldd -v ./tmp/sysroots/x86_64-linux/usr/bin/powerpc-poky-linux/powerpc-poky-linux-ar I see the Library runpath for a shared library is an absolute path to the original

Re: [OE-core] Troubleshooting sstate cache

2018-08-28 Thread Nick Winters
Nick On Tue, Aug 28, 2018 at 12:10 AM Alexander Kanavin wrote: > 2018-08-28 7:53 GMT+02:00 Nick Winters : > > Often when I use an sstate cache from another build, I run into problems > > where builds fail. Usually the failure is a result of not being able to > find > >

[OE-core] Troubleshooting sstate cache

2018-08-27 Thread Nick Winters
Often when I use an sstate cache from another build, I run into problems where builds fail. Usually the failure is a result of not being able to find a shared library. If I delete the sstate cache, the build succeeds, although it is 8 hours later. I switched to using sstate mirrors and had similar