CODEWITHSUNDEEP
rubyrubygemsffi
user1007520
user1007520

Reputation: 341

ERROR: Error installing ffi: ERROR: Failed to build gem native extension

Got the DevKit installed and re-ran the ffi install….got this as an output:

C:\Documents and Settings\******>gem install ffi
Temporarily enhancing PATH to include DevKit...
Building native extensions.  This could take a while...
ERROR:  Error installing ffi:
        ERROR: Failed to build gem native extension.

        C:/Ruby192/bin/ruby.exe extconf.rb
checking for ffi.h... no
checking for ffi.h in /usr/local/include... no
checking for rb_thread_blocking_region()... yes
checking for ruby_thread_has_gvl_p()... yes
checking for ruby_native_thread_p()... yes
checking for rb_thread_call_with_gvl()... yes
creating extconf.h
creating Makefile
make
C:/Ruby192/bin/ruby -e "puts 'EXPORTS', 'Init_ffi_c'"  > ffi_c-i386-mingw32.def
gcc -I. -IC:/Ruby192/include/ruby-1.9.1/i386-mingw32 -I/C/Ruby192/include/ruby-1
.9.1/ruby/backward -I/C/Ruby192/include/ruby-1.9.1 -I. -DRUBY_EXTCONF_H=\"extcon
f.h\"    -O3 -g -Wextra -Wno-unused-parameter -Wno-parentheses -Wpointer-arith -
Wwrite-strings -Wno-missing-field-initializers -Wno-long-long -Wno-declaration-a
fter-statement   -o AbstractMemory.o -c AbstractMemory.c
In file included from AbstractMemory.c:28:0:
compat.h:65:20: warning: extra tokens at end of #ifndef directive
compat.h:69:24: warning: extra tokens at end of #ifndef directive
In file included from AbstractMemory.h:29:0,
                 from AbstractMemory.c:29:
Types.h:68:17: fatal error: ffi.h: No such file or directory
compilation terminated.
make: *** [AbstractMemory.o] Error 1 

Gem files will remain installed in C:/Ruby192/lib/ruby/gems/1.9.1/gems/ffi-1.0.1
0 for inspection.
Results logged to C:/Ruby192/lib/ruby/gems/1.9.1/gems/ffi-1.0.10/ext/ffi_c/gem_m
ake.out
_________________________________________________________________________________

Not sure how to deal with this issue. Kindly help.

Upvotes: 34

Views: 84241

Answers (17)

Taniksha Sharma
Taniksha Sharma

Reputation: 345

Run this: /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Then: brew install cocoapods

Upvotes: 0

Marko S. González B.
Marko S. González B.

Reputation: 63

This worked for me gem install ffi -- --disable-system-libffi on Ubuntu 20.04 (WSL)

Upvotes: 2

Abhishek Sawant
Abhishek Sawant

Reputation: 41

For me, this usually works

gem install ffi -- --disable-system-libffi

Upvotes: 4

hamx0r
hamx0r

Reputation: 4278

On MacOS (Catalina), running brew install libtool first solved the problem for me.

Upvotes: 1

vovan
vovan

Reputation: 1520

Helped me:

sudo apt install build-essential

Debian 9

Ruby 2.3.3

Upvotes: 4

Vijay Raghavan Aravamudhan
Vijay Raghavan Aravamudhan

Reputation: 438

I had to install automake to get it working. Worked on both mac OSX as well as Ubuntu (CI machine).

Upvotes: 0

sahilbathla
sahilbathla

Reputation: 529

sudo apt-get install libffi-dev

This worked for me

Upvotes: 17

ElS arekh
ElS arekh

Reputation: 231

The gem install ffi fails due to the gem trying to build a bundled copy of libffi, which does not work due to assumptions that /usr/bin/env exists and too old libffi copy.

However, you can build the ffi gem against the system libffi - install the packages:

apt install clang make ruby-dev libffi-dev

After that the ffi gem should build:

gem install ffi

Upvotes: 23

Arun Panneerselvam
Arun Panneerselvam

Reputation: 2335

you need this, 

apt-get install ruby2.2-dev

Upvotes: 3

Erwin Kaddy
Erwin Kaddy

Reputation: 967

I got the same problem. In my case, I have not install the DevKit, which can be found: http://rubyinstaller.org/downloads/. After installing DevKit, just follow the instruction https://github.com/oneclick/rubyinstaller/wiki/development-kit and finally it's up and running.

Upvotes: 0

David Vezzani
David Vezzani

Reputation: 1469

Copied from another post:

As stated in Issue with installing ImageMagick and rmagick on Mountain Lion, ffi appears to be configured to look for 'gcc-4.2', so once I updated my Apple command line tools (which I may or may not have needed to do), I created a symbolic link to make the ffi install configuration happy:

sudo ln -s /usr/bin/gcc /usr/bin/gcc-4.2

Upvotes: 2

Grinn
Grinn

Reputation: 5543

For me the fix was running in this order. I'm not sure what all was relevant, but it worked:

gem install ffi --version '1.0.9'

The above failed, but then I could successfully run:

gem install bundler

...and subsequently:

gem install ffi

...which got the latest version (1.6.0 at the time of writing this) and installed it successfully.

Upvotes: 9

konyak
konyak

Reputation: 11706

Put DevKit in front of your PATH, and install again from Windows command prompt.

Upvotes: 0

wantrapreneur
wantrapreneur

Reputation: 420

Installing the 'osx-gcc-installer' worked for me: (osx 10.8)

https://github.com/kennethreitz/osx-gcc-installer/downloads

Upvotes: 4

maniempire
maniempire

Reputation: 801

when the above steps are followed, it might results the following message.

$ bundle install
Fetching source index for https://rubygems.org/
You have requested:
ffi = 1.0.9

The bundle currently has ffi locked at 1.0.11.
Try running `bundle update ffi`

In that case, you can run the 'bundle update ffi' command and the error will be solved.

Upvotes: 7

DVG
DVG

Reputation: 17480

Note that installing version 1.0.9 isn't going to be enough if your bundler keeps trying to go out and grab the latest version. In your gemfile you'll also want to put:

gem 'ffi', '1.0.9'

This should satisfy the dependency for whatever gem is asking for it and let you get up and running.

Upvotes: 6

tommasop
tommasop

Reputation: 18765

Version 1.0.10 has issues compiling on windows.

You can use the 1.0.9

gem install ffi --version='1.0.9'

Upvotes: 16

Related Questions