Cannot install fibers on node 4.0.0 #248
Comments
Jackyjjc
changed the title
|
I have the same problem, too 'npm install fibers --save' ( or-g) gives me that debug logs: 0 info it worked if it ends with ok |
|
My original issue turns out to be XCode being out of date so fibers can't compile properly |
|
I am on linux and have the same problem |
|
I haven't published binaries for the 4.x versions of node yet, but it compiles and runs cleanly on my system. If you're running into issues installing it's a problem with your build environment. You have three options:
|
|
Sorry to bump, but do you have any indication of when you plan to publish binaries for 4.x? |
|
+1. Publishing binaries would be much appreciated! |
|
What is the problem with the build environment? How do we "fix" it? |
|
@jacobfike the error of interest in the original post was "ld: library not found for -lgcc_s.10.5" which is a linker problem missing gcc dependencies. He fixed it by updating XCode. Look at the logs and see what's wrong, but I can assure you it builds cleanly on all supported systems. |
|
For what its worth, I get errors trying to install fibers 1.0.7 on a centos machine with both node 4.1.2 and 4.0.0. Here's the output for 4.1.2 (the 4.0.0 output is similar): |
|
Looks like 3.0.0 and 3.3.1 also don't work for me : ( . Installing with 2.0.2 and 2.5.0 seem to work tho. |
|
There's something wrong with your build environment. The failure is in the node.h included file, which we know is good. |
|
Hmm, I haven't messed around with any internal files. Any idea why that kind of error would happen on one version and not another? I'm using nvm to switch around btw. |
|
It's very tough to say without troubleshooting on your specific machine. I suspect you'll have a problem installing any binary modules, for instance |
|
That does indeed give me errors. I'll have to look into that at some point. Thanks for the tip. |
|
Node 4.1.2 the same problem. What could help? |
|
Figured out my issue. On centos 6, I needed a version of gcc newer than 4.4.7. To upgrade to 4.7.2: Then add this to your user profile (mine was ~/.bash_profile):
|
|
meteor version: 1.2.0.2 I am trying to deploy my meteor project onto aws ec2 by mup, and I just set node version to be 4.1.2 in mup.json. Finally, mup failed to invoke deployment process. Got the following error message: x Invoking deployment process: FAILED |
|
complete error message: npm install
(node) child_process: options.customFds option is deprecated. Use options.stdio instead. npm ERR! fibers@1.0.5 install: npm ERR! Please include the following file with any support request: |
|
@andyhan - the real only version of node that meteor supports is node 0.10.36. Maybe try that version? |
|
@AndyHan1001 You have to use node v0.10.40 – this is the current supported node for meteor 1.2 |
|
@TomFreudenberg - Ah thanks! I'm still on Meteor 1.1. Good to know. Happen to know if they bundled the compiled Fibers for Windows 7 in Meteor 1.2/Node 0.10.40 ?? |
|
@sjmcdowall As I do not have tried meteor on windows myself, I can not guarantee but as I know their build process all necessary elements are "in" on the official MDG releases. |
|
+1 Getting the same problem too on Ubuntu 12.04. |
|
Found a solution for us. This problems occurs when I'm building our project on Travis CI. The VM where our test suites are being ran is using Ubuntu 12.04. Ran the before_install script below and it worked. Just would like to share in case anyone might bump into the same issue. sudo apt-get install python-software-properties -y
sudo add-apt-repository ppa:ubuntu-toolchain-r/test -y
sudo apt-get update -y
sudo apt-get install build-essential -y
sudo apt-get install gcc-4.8 g++-4.8 -y
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.8 20
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.8 20
sudo update-alternatives --config gcc
sudo update-alternatives --config g++
export CC=gcc |
|
Same problems with Node5, v8 apis has changed. |
|
This is scary meteor/meteor#5452 (comment) |
|
@trufae -- what exactly is scaring about that? It is just indicating you need to use the proper version of node for Meteor (0.10.40). Use the right node version, and all is goodness. |
|
Failing to build on Redhat for me. We've got another dependency that requires node v4, so this is causing us a bit of pain. Here's the build output: |
|
@scriby I'd be curious to see what happens if you tried to compile node. Those compiler errors are totally crazy, points to a bad build environment |
|
Any ideas on whether you'd be able to start packaging the node v4 binaries for us poor folk with bad build environments :) ? |
|
@scriby For Fedora/RHEL/CentOS, you must do the following: sudo yum update -y
sudo yum groupinstall "Development Tools" -yMy environment has Node v4 and CentOS 7 and I'm running fibers v1.0.7 fine. |
|
I tried that out, but it didn't seem to help. I don't manage the servers I'm working with right now, so I don't know the ins and outs about how they're configured. We have quite a few servers managed by different groups, so just having the binaries bundled really simplifies things for us. |
|
Here are all the steps I take to install our centos dev machines before installing node (now via nvm): |
|
Binaries are in npm for v5.1.0 |
|
Thanks! Just a heads up that some people probably want to use v4 instead of v5 because it's an LTS release. I'm not sure how much of a pain it is for you to make all the binaries, but it sure is appreciated! |
|
Turns out we couldn't upgrade to node v5 yet due to some other issues. I ended up publishing fibers-scriby@1.0.8 in npm which includes linux32/64 and osx64 binaries. I don't intend to maintain this long term, but it will get us by for now. |
It is frightening because one of the most prominent Node frameworks around is stuck on an ancient major version of Node. |
|
I installed gcc/g++ 4.9, 4.8, 4.7. Nothing helped. Downgraded from node 4.2.3 to node 0.10. And it worked then! Fibers was compiled successfully. What's interesting: fs-ext (someone mentioned in comments) is still failing. My environment: Ubuntu 14.04 LTS. Meteor 1.2.1. |
|
+1 for v4 binaries, please |
|
+1 |
|
+1 npm ERR! fibers@1.0.5 install: |
|
thanks much, @benjsicam -- Happily, Ubuntu 14.04 seems to have GCC 4.8 by default, and has no problem with fibers build & node 4.2 |
|
Could the package maintainers (@laverdet, perhaps?) please confirm whether or not you plan to ever offer binaries for Node 4? If not, our options seem to be one of the following:
Each of these options is either impossible or undesirable for my current infrastructure (We'd prefer to stay on Node 4 for the LTS; upgrading system utils on our server isn't an option; it's clear that Thanks! |
|
Hello guys. yum -y update |
|
Binaries for 4 and 5 are in npm. |
|
😄 Thanks. |
|
Awesome! |
|
Cool |
and others
This is the message I got:
The text was updated successfully, but these errors were encountered: