On Thu, 2013-09-26 at 18:40 -0400, Denys Dmytriyenko wrote: > On Tue, Feb 12, 2013 at 01:36:44PM -0600, Jason Wessel wrote: > > If you never use sstate and always build everything from scratch you > > will never see this problem. However, if you use sstate and build > > directories that last a long time eventually you can end up with the > > scenario where libtool gets a hard coded path in it for sed, and sed > > may not exist. The reason you don't see this problem to often if you > > generally build from scratch is that libtool builds before sed and > > will pickup the host's /bin/sed. > > > > The way to reproduce the issue is: > > > > bitbake some_image > > bitbake -c cleansstate libtool-native > > bitbake sed-native > > bitbake libtool-native > > bitbake -c clean sed-native > > bitbake ANY_PACKAGE_THAT_USES_LIBTOOL_NATIVE > > > > In my case I used modphp, which doesn't exist in the oe-core. You will > > end up with a strange looking error like: > > > > | make[1]: *** [buckets/apr_buckets_alloc.lo] Error 1 > > | > > /opt/build/bitbake_build/tmp/sysroots/x86_64-linux/usr/bin/x86_64-linux-libtool: > > line 981: /opt/build/bitbake_build/tmp/sysroots/x86_64-linux//bin/sed: No > > such file or directory > > Sorry for bringing up this old thread. I'm seeing these and similar errors > now > (nothing really changed in my setup, but some race got them exposed). > > I do see that the proposed patch got merged all the way back in February. But > looks like it wasn't enough. > > I've just seen this error about missing sysroots/x86_64-linux//bin/sed coming > from nativesdk-gettext compilation while calling i686-linux-libtool, i.e. the > nativesdk version of libtool. Should be easy to duplicate the below patch for > libtool from native to nativesdk recipe. > > And another error was from sysroots/x86_64-linux/usr/bin/opkg-build during > do_package_write of some other package. Should opkg-utils-native be patched > the same?
Was this in master with http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=32edeb391f2107bb66b361cdcd4b8d4447731c33 applied? Cheers, Richard _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core