[gentoo-user] installing ffi gem

[gentoo-user] installing ffi gem

[Matt Harrison]

[-- Attachment #1.1: Type: text/plain, Size: 711 bytes --]

I've just tried setting up a new development machine and I'm stuck installing the ffi
gem for ruby.

According to a bug I found (can't find it now I'm afraid) the gentoo devs do not
support installing gems via the gem command and directed the user to use the
dev-ruby/ffi package. Unfortnately, that package is absolutely ancient and unusable.

Anyway, I've got the ffi library install from portage, but when I try to `gem install
ffi`, I get the output seen in the attachement.

The same gem installs just fine on an ubuntu box, but...well it's ubuntu and I don't
want to use that (besides it's just a VM).

I'd really like to get this fixed so I can get started on a new project.

Grateful for any help

Matt

[-- Attachment #1.2: output.txt --]
[-- Type: text/plain, Size: 8014 bytes --]

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

        /usr/bin/ruby18 extconf.rb
checking for ffi_call() in -lffi... yes
checking for ffi_prep_closure()... yes
checking for ffi_raw_call()... yes
checking for ffi_prep_raw_closure()... yes
checking for rb_thread_blocking_region()... no
checking for ruby_thread_has_gvl_p()... no
checking for ruby_native_thread_p()... no
checking for rb_thread_call_with_gvl()... no
creating extconf.h
creating Makefile

make
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c DynamicLibrary.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c Buffer.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c MemoryPointer.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c StructByReference.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c StructByValue.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c StructLayout.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c Thread.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c DataConverter.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c Types.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c AbstractMemory.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c Platform.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c ArrayType.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c ffi.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c LastError.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c FunctionInfo.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c MappedType.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c Variadic.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c Function.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c Call.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c Type.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c Pointer.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c MethodHandle.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c ClosurePool.c
i686-pc-linux-gnu-gcc -I. -I. -I/usr/lib/ruby/1.8/i686-linux -I. -DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -march=i686 -pipe -fno-strict-aliasing  -fPIC  -I/usr/lib/libffi-3.0.9/include   -Wno-declaration-after-statement   -c Struct.c
i686-pc-linux-gnu-gcc -shared -o ffi_c.so DynamicLibrary.o Buffer.o MemoryPointer.o StructByReference.o StructByValue.o StructLayout.o Thread.o DataConverter.o Types.o AbstractMemory.o Platform.o ArrayType.o ffi.o LastError.o FunctionInfo.o MappedType.o Variadic.o Function.o Call.o Type.o Pointer.o MethodHandle.o ClosurePool.o Struct.o -L. -L/usr/lib -Wl,-R/usr/lib -L. -Wl,-O1 -Wl,--as-needed -rdynamic -Wl,-export-dynamic -Wl,--no-undefined     -Wl,-R -Wl,/usr/lib -L/usr/lib -lruby18 -lffi  -lffi   -lrt -ldl -lcrypt -lm   -lc
Thread.o: In function `rbffi_thread_blocking_region':
Thread.c:(.text+0x115): undefined reference to `pthread_create'
Thread.c:(.text+0x159): undefined reference to `pthread_join'
Thread.o: In function `cleanup_blocking_thread':
Thread.c:(.text+0x2f6): undefined reference to `pthread_kill'
Thread.o: In function `rbffi_blocking_thread':
Thread.c:(.text+0x348): undefined reference to `pthread_testcancel'
collect2: ld returned 1 exit status
make: *** [ffi_c.so] Error 1


Gem files will remain installed in /usr/lib/ruby/gems/1.8/gems/ffi-1.0.7 for inspection.
Results logged to /usr/lib/ruby/gems/1.8/gems/ffi-1.0.7/ext/ffi_c/gem_make.out
Building native extensions.  This could take a while...

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-user] installing ffi gem

[Alan McKinnon]

Apparently, though unproven, at 01:57 on Friday 22 April 2011, Matt Harrison 
did opine thusly:

> I've just tried setting up a new development machine and I'm stuck
> installing the ffi gem for ruby.


The gentoo dev most active with ruby gems is flameeyes. He's a prolific 
blogger and documents everything he is going through in full painful detail 
here:

http://blog.flameeyes.eu

The most current info on how to deal with gems on gentoo will be found there 
IMHO




> 
> According to a bug I found (can't find it now I'm afraid) the gentoo devs
> do not support installing gems via the gem command and directed the user
> to use the dev-ruby/ffi package. Unfortnately, that package is absolutely
> ancient and unusable.
> 
> Anyway, I've got the ffi library install from portage, but when I try to
> `gem install ffi`, I get the output seen in the attachement.
> 
> The same gem installs just fine on an ubuntu box, but...well it's ubuntu
> and I don't want to use that (besides it's just a VM).
> 
> I'd really like to get this fixed so I can get started on a new project.
> 
> Grateful for any help
> 
> Matt

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] installing ffi gem

[kashani]

On 4/21/2011 4:57 PM, Matt Harrison wrote:
> I've just tried setting up a new development machine and I'm stuck installing the ffi
> gem for ruby.
>
> According to a bug I found (can't find it now I'm afraid) the gentoo devs do not
> support installing gems via the gem command and directed the user to use the
> dev-ruby/ffi package. Unfortnately, that package is absolutely ancient and unusable.
>
> Anyway, I've got the ffi library install from portage, but when I try to `gem install
> ffi`, I get the output seen in the attachement.
>
> The same gem installs just fine on an ubuntu box, but...well it's ubuntu and I don't
> want to use that (besides it's just a VM).
>
> I'd really like to get this fixed so I can get started on a new project.
>
> Grateful for any help
>
> Matt

Install RVM, make it part of your shell, then install the ruby and gems 
of your choice. That way you leave the system Ruby alone and can develop 
with the versions you want. You can even do multiple versions of ruby 
and various gems for working on many different projects at once.

https://rvm.beginrescueend.com/rvm/install/

	It really is the simplest way to build a dev environment and maintain 
it for Ruby.

kashani

Re: [gentoo-user] installing ffi gem

[Matt Harrison]

[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]

On Thu, Apr 21, 2011 at 05:33:05PM -0700, kashani wrote:
> On 4/21/2011 4:57 PM, Matt Harrison wrote:
> > I've just tried setting up a new development machine and I'm stuck installing the ffi
> > gem for ruby.
> >
> > According to a bug I found (can't find it now I'm afraid) the gentoo devs do not
> > support installing gems via the gem command and directed the user to use the
> > dev-ruby/ffi package. Unfortnately, that package is absolutely ancient and unusable.
> >
> > Anyway, I've got the ffi library install from portage, but when I try to `gem install
> > ffi`, I get the output seen in the attachement.
> >
> > The same gem installs just fine on an ubuntu box, but...well it's ubuntu and I don't
> > want to use that (besides it's just a VM).
> >
> > I'd really like to get this fixed so I can get started on a new project.
> >
> > Grateful for any help
> >
> > Matt
> 
> Install RVM, make it part of your shell, then install the ruby and gems 
> of your choice. That way you leave the system Ruby alone and can develop 
> with the versions you want. You can even do multiple versions of ruby 
> and various gems for working on many different projects at once.
> 
> https://rvm.beginrescueend.com/rvm/install/
> 
> 	It really is the simplest way to build a dev environment and maintain 
> it for Ruby.
> 
> kashani

Thanks Alan and kashani,

I'll take a look at both, if I can't find anything on his blog I'll give RVM a go :)

Thanks guys

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-user] installing ffi gem

[skiarxon]

[-- Attachment #1: Type: text/plain, Size: 40 bytes --]

That one? http://bugs.gentoo.org/327835

[-- Attachment #2: Type: text/html, Size: 85 bytes --]

[gentoo-user] Re: installing ffi gem

[Hans de Graaff]

On Fri, 22 Apr 2011 00:57:13 +0100, Matt Harrison wrote:

> I've just tried setting up a new development machine and I'm stuck
> installing the ffi gem for ruby.
> 
> According to a bug I found (can't find it now I'm afraid) the gentoo
> devs do not support installing gems via the gem command and directed the
> user to use the dev-ruby/ffi package. Unfortnately, that package is
> absolutely ancient and unusable.

That is correct, we recommend to use our native Gentoo packages when 
present.

If you have a problem with a package, then please file a bug report at 
https://bugs.gentoo.org/  ffi-0.6.3-r1 should be usable.

> Anyway, I've got the ffi library install from portage, but when I try to
> `gem install ffi`, I get the output seen in the attachement.

Yes, you are trying to install a version of the ffi gem that is not 
compatible with your ruby version. ffi-0.6.3 is the latest version that 
reliably works with ruby 1.8. The ffi-1.x series never worked reliably 
with ruby 1.8, and the latest version have officially removed support for 
it and only work with ruby 1.9. This is also the reason that ffi-0.6.3 is 
the latest version in the tree.

Kind regards,

Hans

[gentoo-user] Re: installing ffi gem

[Hans de Graaff]

On Thu, 21 Apr 2011 17:33:05 -0700, kashani wrote:


> Install RVM, make it part of your shell, then install the ruby and gems
> of your choice. That way you leave the system Ruby alone and can develop
> with the versions you want. You can even do multiple versions of ruby
> and various gems for working on many different projects at once.

Please note that Gentoo also supports multiple ruby implementations out 
of the box (ruby 1.8, ruby enterprise edition, jruby currently stable, 
ruby 1.9 unfortunately still masked, rubinius forthcoming).

Kind regards,

Hans

Re: [gentoo-user] Re: installing ffi gem

[kashani]

On 4/21/2011 9:54 PM, Hans de Graaff wrote:
> On Thu, 21 Apr 2011 17:33:05 -0700, kashani wrote:
>
>> Install RVM, make it part of your shell, then install the ruby and gems
>> of your choice. That way you leave the system Ruby alone and can develop
>> with the versions you want. You can even do multiple versions of ruby
>> and various gems for working on many different projects at once.
>
> Please note that Gentoo also supports multiple ruby implementations out
> of the box (ruby 1.8, ruby enterprise edition, jruby currently stable,
> ruby 1.9 unfortunately still masked, rubinius forthcoming).

	It's not about which ruby you're installing on the system, really 
anything other than 1.8.7 as system Ruby is a pain in the ass at this 
point.

kashani@gentoo64 ~ $ rvm list
rvm rubies

    rbx-head [ ]
    ree-1.8.7-2011.03 [ x86_64 ]
    ruby-1.9.2-p180 [ x86_64 ]
=> ruby-1.8.7-p334 [ x86_64 ]

	Using RVM I can have all version and implementations of Ruby and 
multiple gem sets per Ruby as well. That way I can work on 
ruby-1.8.7@rail2 app or switch to ruby-1.92@rails3 which keep the gems 
separate. Also I avoid breaking the system when doing wacky things in my 
dev environment.

kashani

[gentoo-user] Re: installing ffi gem

[Hans de Graaff]

On Thu, 21 Apr 2011 23:12:51 -0700, kashani wrote:

> On 4/21/2011 9:54 PM, Hans de Graaff wrote:

>> Please note that Gentoo also supports multiple ruby implementations out
>> of the box (ruby 1.8, ruby enterprise edition, jruby currently stable,
>> ruby 1.9 unfortunately still masked, rubinius forthcoming).
> 
> 	It's not about which ruby you're installing on the system, really
> anything other than 1.8.7 as system Ruby is a pain in the ass at this
> point.

This is not about the system ruby, I agree that ruby 1.8.7 is currently 
the only sane choice for that.

> 	Using RVM I can have all version and implementations of Ruby and
> multiple gem sets per Ruby as well. That way I can work on
> ruby-1.8.7@rail2 app or switch to ruby-1.92@rails3 which keep the gems
> separate. Also I avoid breaking the system when doing wacky things in my
> dev environment.

The Gentoo setup can do this too. It install gems for all supported, 
desired, ruby implementations, and keeps separate gem hierarchies for 
each ruby implementation, so you can use different ruby implementations 
for different applications if you want.

This is all part of the ruby-ng.eclass, which all packages in testing 
use, and which is currently being pushed into stable.

Kind regards,

Hans