-
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
meta-nodejs error with Yocto #44
Comments
I noticed that you have
This repository does not have What is the source for your |
Also, same advice applies as given in issue #9
|
Thanks for your quick response. I am testing in a local copy, that's why you don't see it in the main branch. I just downloaded your code and install it. In regards of the bash, I am on that, so it is ok. But here is the interesting part. I have one of your prev version (I beleive) BUT I am using it only in a recipe (instead of a layer) and it compiles and works without a problem. nodejs_diff.txt |
What Node.js version are you trying to build? |
0.12 |
There have been OpenSSL compilation issues with Node.js 0.x outside Yocto projects too. I'm currently testing 0.12 builds in my build server. |
Please try with latest repo version for
|
Hurray!, It works! I tested back in fido and it works too! |
Glad to hear! I'm closing this issue as resolved. |
I tried putting the layer as indicated and the system indicated an error during compiling.
Details:
Using Yocto-fido
Build Configuration:
BB_VERSION = "1.26.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-14.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "beaglebone"
DISTRO = "poky"
DISTRO_VERSION = "1.8.2"
TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard cortexa8"
TARGET_FPU = "vfp-neon"
meta
meta-yocto
meta-yocto-bsp
meta-nodejs = "fido:900d7d6b59c36b2bdbd1c85febec99e80ab54f95"
I add nodejs in the local.conf as follows
IMAGE_INSTALL_append = "nodejs"
Then I run bitbake nodejs and the system report the next error
... make[1]: execvp: printf: Argument list too long
I gave a try with Yocto-Krogoth with same results
I saw that this issue was patched before
https://github.com/imyller/meta-nodejs/issues/9 but it seems that is back, is that the case?
The text was updated successfully, but these errors were encountered: