How to install ruby-debug when needing necessary libraries and/or headers

S

15

51

My Rails is 3.2.1.4, Ruby is 1.9.3p448.

I got an error when I install ruby-debug:

Building native extensions.  This could take a while...
ERROR:  Error installing ruby-debug:
        ERROR: Failed to build gem native extension.

    /home/hxh/.rvm/rubies/ruby-1.9.3-p448/bin/ruby extconf.rb
Can't handle 1.9.x yet
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers.  Check the mkmf.log file for more
details.  You may need configuration options.

Provided configuration options:
        --with-opt-dir
        --without-opt-dir
        --with-opt-include
        --without-opt-include=${opt-dir}/include
        --with-opt-lib
        --without-opt-lib=${opt-dir}/lib
        --with-make-prog
        --without-make-prog
        --srcdir=.
        --curdir
        --ruby=/home/hxh/.rvm/rubies/ruby-1.9.3-p448/bin/ruby


Gem files will remain installed in /home/hxh/.rvm/gems/ruby-1.9.3-p448/gems/linecache-0.46 for inspection.
Results logged to /home/hxh/.rvm/gems/ruby-1.9.3-p448/gems/linecache-0.46/ext/gem_make.out

Who can tell me where the error is?

Seismic answered 31/10, 2013 at 2:21 Comment(1)

Updating ruby through brew install ruby fixed this for me. – Razzledazzle 22/3, 2018 at 7:49

S

20

The error is in the mkmf.log file. That file should be located at /home/hxh/.rvm/gems/ruby-1.9.3-p448/gems/linecache-0.46/ext/linecache/mkmf.log.

If not, you can use

sudo find / -name mkmf.log

to find it.

To troubleshoot further, see "How to install Nokogiri Ruby gem with mkmf.log saying libiconv not found?"

Supertax answered 6/12, 2013 at 22:3 Comment(3)

But what about when there is no mkmf.log file for the gem in question? For me, there's mkmf.log files for many other gems but not the one that's having a problem. – Landrum 18/8, 2016 at 21:46

@Landrum did you get any extra info in the error message? near the bottom i got To see why this extension failed to compile, please check the mkmf.log which can be found here: ... followed by a full path to the specific .log file – Nichani 18/9, 2016 at 0:47

Like I said there was no mkmf.log file in the location it specified. I think I ended up restarting everything and the problem went away. – Landrum 19/9, 2016 at 16:51

G

20

I am using Mac El Capitan. In my case it was caused by the missing developer tool. I solved it by installing the developer tool via xcode-select --install. After that bundle install worked fine again.

Guerdon answered 10/3, 2016 at 3:57 Comment(1)

Same here on Sierra, and my problem gem was Nokogiri. – Blabber 17/8, 2017 at 0:48

C

18

You're most likely missing some file headers (e.g. zlib or libiconv), so try installing them.

Linux: sudo apt-get install libz-dev libiconv-hook1 libiconv-hook-dev

OS X: brew install libiconv && xcode-select --install

Otherwise check your mkmf.log file for more specific details.

Chromaticity answered 9/7, 2016 at 1:15 Comment(2)

Or if using Alpine Linux: apk add -build-base – Impression 23/7, 2019 at 13:13

found some good docs at nokogiri.org/tutorials/…. it would be: apk add build-base – Copernicus 19/10, 2021 at 22:55

D

8

I was facing the same issue running MacOS Big Sur version 11.1 and Xcode Version 12.4 (12D4e). In my case there was no command-line tool selected in Xcode.

I just followed the following steps to fix the problem:

Start Xcode.
Open the preferences using ⌘+,.
Select the Locations tab.
Select command-line tool (Xcode 12.4 12D4E in my case).
Run sudo gem install cocoapods (in my case).

Depressomotor answered 29/1, 2021 at 12:30 Comment(0)

M

6

It seems to be a issue with permission of gcc.. however, if you're using OS X, you may encounter this issue if you've updated your XCode but haven't agree to their terms & conditions yet.. try typing gcc in your terminal would show you what if you've agreed.

Monetmoneta answered 28/9, 2015 at 13:47 Comment(0)

V

4

My mkmf.log showed that gcc (4.8.2 I think) didn't like a specific argument that was being used by atomic on

$ gem install atomic

So I had a very similar situation. The answer for me was to upgrade gcc/gcc-libs and lib tool.

I use Arch linux, and only Arch linux. The proper way to do this is to run

$ sudo pacman -Syu

which upgrades all system packages.

I installed Rails and hadn't run a system update since, which is where the issue came from. In most other *nix distros, you would update to the latest version of these packages by name, i.e. with apt, it would be something along the lines of

$ sudo apt-get update

followed by

$ sudo apt-get upgrade {package-name}

Verity answered 11/11, 2014 at 17:0 Comment(3)

This answer can be improved by providing instructions for how to upgrade those libraries. – Illmannered 16/4, 2015 at 17:23

I run Arch linux which plays by it's own rules in many ways, including package management, and I can't determine what operating system the asker is using at a glance. – Verity 1/5, 2015 at 12:47

gem install atomic did it for me =) – Equiponderance 13/4, 2017 at 19:38

K

4

For what it's worth, using Ruby 2.0.0 I was having this problem on OSX 10.10.

I ended up running brew update, which resolved some conflicts, then installed the gem and it was fine.

Kaon answered 2/12, 2014 at 16:34 Comment(0)

V

4

The answer of kenorb worked for me on Ubuntu 16.04 when I was trying installing rails! Thanks! I followed these steps below for installing rails:

sudo apt-get install ruby-full
sudo apt-get install libz-dev libiconv-hook1 libiconv-hook-dev
sudo gem install rails

Veracruz answered 13/11, 2016 at 3:3 Comment(1)

facing same issue in LinuxMint. I can install rails after follow your instruction. Thanks1 – Induline 25/12, 2017 at 4:9

G

4

I had the issue because gcc wasn't available on my machine.

Fixed it by installing gcc.

sudo apt install build-essential

Gobelin answered 6/6, 2020 at 11:9 Comment(0)

M

2

This worked for me. Nokogiri was the problem.

Try the following if you are using Alpine-Linux(or equivalent command for your OS):

apk add build-base

And then install Nokogiri using:

gem install nokogiri -- --without-pkg-config --with-libxml-2.0-config

Mountainside answered 30/7, 2020 at 14:50 Comment(1)

Good docs for nokogiri: nokogiri.org/tutorials/… – Copernicus 19/10, 2021 at 22:58

B

2

Took me a while to successfully install it.

Install cocoapods with HomeBrew brew install cocoapods && brew link --overwrite cocoapods
Verify your cocoapods version pod --version

Breakwater answered 30/9, 2022 at 20:43 Comment(1)

If Brew not Installed check brew.sh then add export PATH=/opt/homebrew/bin:$PATH in .zshrc file – Mcgowan 8/2, 2023 at 8:7

T

1

This is probably happening because your computer has an older version of Ruby, so first update Ruby. This worked for Ruby 2.6.3+.

Open terminal and enter:

curl -L https://get.rvm.io | bash -s stable

Then:

rvm install ruby-2.6

This will install Ruby for you if it wasn't already installed, then update Ruby to the new version:

rvm use ruby-2.6.3

This will possibly fix your issue. You can now enter:

sudo gem install cocoapods
pod setup

If RVM is not installed in your system, then use:

$HOME/.rvm/scripts/rvm
rvm

Truant answered 26/2, 2021 at 12:19 Comment(0)

R

-1

The problem is resolved with next command: sudo apt install build-essential

Roseroseann answered 11/12, 2020 at 12:30 Comment(0)

E

-1

Install RVM and use it to install Ruby 2.6.x:

curl -sSL https://get.rvm.io | bash
rvm install 2.6.x
rvm use ruby-2.6.x

Now try and it should work:

sudo gem install cocoapods

Emmanuelemmeline answered 8/12, 2021 at 21:39 Comment(0)

S

-1

This worked for me:

sudo apt-get install libmysqlclient-dev

Sismondi answered 25/1, 2022 at 13:40 Comment(1)

Welcome to SO! Please read "How to Answer" and "Explaining entirely code-based answers". While this might be technically correct it doesn't explain why it solves the problem or should be the selected answer. We should educate along with helping solve the problem. In particular, explain why installing the MySQL-client dev help, especially since its a very round-about way of solving the problem. – Apostrophize 30/1, 2022 at 21:6

Recommended topics

Hot tags