openembedded/meta-openembedded

Kirkstone branch build is currently broken when trying to compile any npm recipe

Closed this issue · 5 comments

aurelihein commented

If you try to compile a recipe that use npm on yocto poky kirkstone and meta-openembedded kirkstone branch the build will fail with :
ERROR: Nothing PROVIDES 'nodejs-oe-cache-native' (but /srv/yocto/poky/**** DEPENDS on or otherwise requires it). Close matches:", " nodejs-native", "ERROR: Required build target '****' has no buildable providers."
It seems introduced by the last commit on yocto poky kirkstone : HERE
It works though if you switch from kirkstone to master meta-openembedded
Am I sharing this in the right place ?
Thanks for your feedback
Aurelien BOUIN

shr-project commented

This should be reported in oe-core ML https://lists.openembedded.org/g/openembedded-core (I've already replied there https://lists.openembedded.org/g/openembedded-core/message/170599)

IMHO nodejs-oe-cache-native should be migrated from meta-oe to oe-core (in master and then in kirkstone as well), because now npm.bbclass in oe-core is unusable without meta-oe layer.

Well it already depends on nodejs-native which is from meta-oe, so at least for now we can just add nodejs-oe-cache-native to kirkstone branch as well, I've sent patch for that to oe-devel ML.

  • 👍1
shr-project commented

@akuster meta-oe-cache-native cherry-picked to meta-oe/kirkstone sent https://lists.openembedded.org/g/openembedded-devel/message/98787

aurelihein commented

Thank you @shr-project I guess we just need to wait now 👍

mvargasevans commented

Hi
Stumbled with this today - It seems unresolved, no?