-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
recipe: Node.js v7 cross-compilation dependency issues #56
Comments
Documented Node v7 requirements to master branch README in commit 0b66df5 Hopefully we can resolve the issue and remove this doc before merging v7 in |
No progress yet. Looks like we are going to have to kindly ask Yocto to include While I hoped not to, I'm now considering merging v7.x Node.js recipes to krogoth and jethro branches with this dependency requirement. |
Node.js v7.x.x is now in Unfortunately |
Hi, I struggled a bit finding out this dependency was needed. and for the record, on my Ubuntu 14.04 64bit host, I also had to install : |
I'm using rocko..what should i do before bitbake core-minimal, in order to manage working with nodejs>=6 and npm in my linux? |
Node.js v7 ships with new version of V8 Javascript engine that requires native (host) compilation of
mkpeephole
utility.mkpeephole
is fundamental to the design of the new ignition interpreter in V8.Unfortunately V8 mandates building
mkpeephole
tool with 32-bit (!) native toolchain. In addition, if opting to build with external openssl and/or zlib, the compilation requires 32-bit versions of those as well for the native toolchain.Installing
g++-multilib
package to host system allows building Node.js v7 recipes for most embedded targets, but such host system dependency is not included by default in Yocto 2.1 build system requirements.Different options for resolving this both in Node.js+V8 upstreams and within OpenEmbedded tools are currently being explored. Good ideas are welcome!
This issue has been opened as proper place to continue the discussion started in issue comments:
c54ce2a#commitcomment-19620853
The text was updated successfully, but these errors were encountered: