-
Notifications
You must be signed in to change notification settings - Fork 35
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
Ekam can't find 'capnp.node' when reading 'node-capnp.ekam-manifest' for a Sandstorm build #18
Comments
We actually pull the node header out of Meteor, because we want to use exactly the version bundled with Meteor. It seems like you have Meteor installed, though, so I'm not sure what's wrong. Maybe the Meteor package manager hasn't actually downloaded the version of the packages to which Sandstorm is pinned? That might be fixed by going under the shell directory and simply typing @jparyani is currently working on updating us to a newer version of Meteor which may very well cause this problem to go away. |
We've updated to a newer Meteor version which means the code path for finding |
https://asciinema.org/a/7F427JVyE6FGTFMYTtcjWxdPX arm64 for muti gazzilion core servers would be a plus.. takes a bit ... to get 1 for now scarthing my packages list down... it will fail on arm64 with 2 gis , https://cloud.scaleway.com |
Hi @necrose99, Sorry, I don't understand what you're asking. This issue is long-obsolete, so I'm going to close it, but if you have a different problem, could you open a new issue? |
Hi,
I'm not entirely certain if this should be a Sandstorm bug, an Ekam bug, or an node-capnp bug, so it might be that I'm doing something stupid w.r.t. to your custom build system. Please forgive if that's the case, and I'll gladly file the bug wherever it best should go.
It seems that Ekam can't find the
capnp.node
file (fromnode-capnp/node-capnp.ekam-manifest
, fromsandstorm/sandstorm.ekam-manifest
) due to compilation errors from being unable to find<node.h>
. (I assume the node header should be fromnodejs-dev
, which I have installed. This is on a fresh Debian Jessie system.)The relevant build error is:
And yet I've got
/usr/include/nodejs/src/node.h
with the requiredNODE_MODULE
macro… is it possible that Ekam isn't symlinking in the headers directory fornodejs-dev
correctly, because it's named in a directory namesrc
in this case? I thought that Ekam would still find headers in asrc/
dir?In case it's needed, here's the full build output:
The text was updated successfully, but these errors were encountered: