Closed piranna closed 9 years ago
I've found that although I'm using nvm
on SemaphoreCI to use Node.js 0.12.7, since NodeOS build process internally exec npm
it's still using 0.10.25. Could this be the problem?
Yes, that's most likely the problem given the bewildering combination of gyp ERR! node -v v0.10.25
and the missing fcntl
header. The fcntl
header should been included via v8 headers for any node <= v0.10, but here is missing, making it seem like it's compiling against a newer node.
Also, we shouldn't run into any issues converting to Nan, but kexec predates Nan, and since kexec is only a few lines of code, I guess no one has found the need yet.
I'm fine with dropping support for Node v0.8. We could even drop support for Node v0.10 if need be.
I've written to SemaphoreCI looking for advice since I need this working for my bachelor thesis.
I don't think it would be a good idea to drop Node.js 0.10, it's still available by default on Ubuntu 14.04 LTS...
Seems it's a problem in SemaphoreCI, I'll update the issue when I get more info.
Definitely it was an error on SemaphoreCI, I've fixed it by disabling nvm
and installing Node.js 0.12 globally from NodeSources repository. I think this issue can be closed (except is you want to talk about the nan
thing... :-) ).
I have configured SemaphoreCI to generate all releases, but
kexec
fails to build there while on my laptop it works correctly. I'm not sure what's the reason, but I think could be due to lack of some includes or something similar since I'm building it against the cross-compiler generated for NodeOS based on musl. SemaphoreCI use a raw instance of Ubuntu 14.04, while my laptop has Ubuntu 15.10:By the way: why are you (still) using directly the v8 APIs instead of standard
nan
macros?