-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Add libgmp-dev as an Ubuntu requirement #3509
Comments
This happens for me only with ruby-2.2.3 If it is the same for you, maybe you could edit the post so that rvm guys have an easier work. |
Ok - I just did a test on a brand new VM (Ubuntu 14.04.3 LTS) . This is not an issue with ruby-2.2.2 . |
But I can reproduce on ruby-2.2.3 |
I can confirm that I had this issue on Ruby-2.2.3. I wasted hours trying out solutions on Stack Overflow and other sites, but finally found the solution here: https://groups.google.com/forum/#!topic/nokogiri-talk/cMUdmGRVYos Thanks Lars Kanis for the solution. I had to do the following: sudo apt-get install libgmp-dev Sorry, this is my first post here, so I am not good at formatting. |
This is an issue with the binary hosted at https://rubies.travis-ci.org/ubuntu/14.04/x86_64/ruby-2.2.3.tar.bz2 To wit:
This is evidence that the 2.2.3 binary is linking against libgmp, where that hadn't been done in the past. Who built this binary? Is it under the rvm team's control? It's causing problems with the installation of C extensions, as indicated by these threads: |
I had this issue as well for ruby 2.2.3 and installing this library definitely fixed the issue. Can this be documented on the installation page? |
Bump. |
This issue is also causing problems with my gem hitimes. I have had multiple folks report hitimes as unable to install and this is the culprit. Has anyone contacted @travis-ci about this? It sounds to be that there needs to be some additional coordination between RVM and @travis-ci if one is going to provide the ruby installation, and the other is going to use it. |
@copiousfreetime I've stopped by and mentioned it in the #travis irc channel but I don't know of any formal liaison to inform. |
The alternative is to remove the Travis URLs from RVM's config.
|
Having the same issue with 2.2.4. |
Installing libgmp-dev is the only thing that let me proceed with 2.2.3. Thanks! |
For anyone that finds this thread, please know there's a workaround, which is to install your ruby with |
Please note that I've raised a new issue at travis-ci/travis-rubies#15 which appears to be a related repo. |
Confirming "apt-get install libgmp-dev" allowed me to install msgpack on 2.2.4. |
@mpapis Should I add |
I'd prefer if Travis binaries either were no longer installed by RVM or Adding libgmp as a dependency for RVM seems like a defensive decision, but
|
@raelgc I think it was added already in #3564 @flavorjones RVM2 will have more advanced installation method that will be able to detect dependencies at runtime and install them ... at least this is the plan, till then we have the extra dependency in RVM1. |
Install libgmp-dev as a workaround for the missing dependency of rvm. See also: rvm/rvm#3509
Install libgmp-dev as a workaround for the missing dependency of rvm. See also: rvm/rvm#3509
Install libgmp-dev as a workaround for the missing dependency of rvm. See also: rvm/rvm#3509
gem install nokogiri |
RVM installs a binary ruby, which is linked to libgmp, but doesn't install the libgmp-dev package. Ruby runs fine this way, but extensions will not compile.
rake-compiler-dock via @larskanis
As a result it is not possible to install gems like nokogiri or atomic (which is necessary for rails).
Installs of these gems fail with this error:
gem_make.out:
mkmf.log:
System infomation
The text was updated successfully, but these errors were encountered: