Build fails on io.js 1.0.2 #203
Comments
|
I can confirm this issue, I am experiencing the same issue. |
|
Issue #185 is a duplicate of this issue. |
|
Fix: |
|
any chance this'll get fixed? |
|
the bug reappeared? |
|
@iMote yep, have exactly same message while trying to install fibers using iojs 1.4.3 (from nvm) on mac os |
|
same for me, so i'm on nodejs v0.12 now :p @yamalight |
|
I can confirm, this also happens for me. |
|
Having this issue as well, preventing me from switching to io.js. |
|
Still having the issue with iojs v1.6.1 |
|
Just as a heads up, this makes NativeScript impossible to use with iojs. |
|
Just found forked version here. eiriklv@18a1416 I haven't tried it yet, but it might fix this issue. |
|
Sorry for dragging my feet on this. While looking into this bug I discovered some crazy weirdness going on with the stack guard in node 0.10.x and I didn't want to push out a half fix. While I've isolated the issue, I haven't discovered a fix. node 0.12.x & io.js are fine though so I'm going to forget about it. Could you guys take a quick peek at the stack-guard branch and let me know if it works for you. It would be super helpful if you guys could post the output of |
|
|
@laverdet just tried running tests in stack-guard branch with latest iojs on my machine, all seem to pass: |
|
test-1 test-2 test-3 |
|
Please advice, what am I doing wrong... gives the same
|
|
@pstadler & @redism interesting that you're getting failures in node 0.12.x. I'm running the same machine configuration (OS X, x64) and mine is fine. This is with a fresh build of fibers, right? Could you try modifying |
|
Just to report that Ifixed the problem. Currently |
|
@laverdet I've tested as you told, but it still failed. But after changing Hope this helps. |
|
For what it's worth, I have issues with node 0.12 failing two stack overflow tests: However it works fine in io.js: |
|
FWIW, I seem to get different results from everybody else, in that Same result with io.js v1.6.2. With node v0.12.2, both |
|
Just a quick note. v0.12.2 -> works fine; except warnings iojs-v1.7.1 -> fails on fibers.o |
|
On OSX 10.10 x64 iojs v1.8.1 $ npm test
already-running.js: pass any update on this @laverdet |
|
The stack-guard branch is already merged to master so I'm guessing some of the experiments here are no longer necessary. I tried node-fibers 1.0.5 with the current iojs release (2.1.0) and found a different compile-time problem; see #227. |
|
Any idea when a new version containing the changes merged with stack-guard is gonna be released? |
|
Fibers should compile just fine on iojs at this point. |
|
@laverdet |
|
Any solution for this? I can't install fibers and I can't deploy meteor app. node -v => v4.2.1 |
|
@jpmelnik -- The only supported node version for meteor is 0.10.40 for Meteor 1.2.1. It also contains (the meteor package) a forked version of fibers especially for Meteor .. you should (need) to be using those versions on any meteor deployment I would think. |
|
Ok, I changed the version of Node and I get the same issue:
(node) child_process: options.customFds option is deprecated. Use options.stdio instead. npm ERR! [email protected] install: |
|
I get new issue:
(node) child_process: options.customFds option is deprecated. Use options.stdio instead. Error: spawn EACCES npm ERR! [email protected] install: |
|
@jpmelnik I have the same issue right now, same versions as you. What did you do to fix it? |
|
You're having an issue compiling fibers on an abandoned version of iojs from over a year ago? |
|
Not iojs, I said nodejs. I mentoined jpmelnik in my comment (he listed his versions above). And it is really not that weird because you could be coming back to a very old project only to run into issues when you updated something else (which is my case right now). Anyway, I found the fix somewhere else. You need the exact version of node.js being |
|
Ahh, was this under a previous version of Meteor then? Fibers 1.0.5 is really old so if your error message says 1.0.5 you should consider updating from npm. |
|
@tolgap -- Is this also a Meteor app? If so what version and how are you running it. Prior to Meteor 1.4 (and I have no idea if its still true) -- MDC included their own forked version of Fibers (1.0.5) without (alas) much binary support so moving to almost any production environment meant you had to have a full development environment to compile their version of Fibers. If this is 1.4+ (and I hope it is) I don't know what version of Fibers Meteor now includes in a new project, etc. or even if the hacked Fibers is still needed or if the stock one is ok. You may want to ask the Meteor forum. Of course if this is NOT Meteor .. never mind. :) |
|
@sjmcdowall Yes this is a meteor app. I do a manual deployment. It's running version 1.1.0.2. But the fix was (as said above) that I was using the wrong version of node/npm. |
Attaching build log.
nodejs/node#456
The text was updated successfully, but these errors were encountered: