Subject:
Re: [ruby-ffi] gem install ffi fails to build native extensions
From:
Chuck Remes
Date:
5/11/11 4:05 PM
To:
ruby-ffi@googlegroups.com


On May 11, 2011, at 11:01 AM, lil'b wrote:

> Good morning everyone,
> 
> When I try to install the FFI gem on my engineyard instance, I get the
> following failure:
> 
> <snip>
> i686-pc-linux-gnu-gcc -I. -I/usr/include/ruby-1.9.1/i686-linux -I/usr/
> include/ruby-1.9.1/ruby/backward -I/usr/include/ruby-1.9.1 -I. -I/usr/
> lib/ruby/gems/1.9.1/gems/ffi-1.0.7/ext/ffi_c/libffi/include -
> DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -
> march=pentium-m -pipe -mno-tls-direct-seg-refs -fno-strict-aliasing -
> fPIC -Wno-declaration-after-statement   -o Types.o -c Types.c
> i686-pc-linux-gnu-gcc -I. -I/usr/include/ruby-1.9.1/i686-linux -I/usr/
> include/ruby-1.9.1/ruby/backward -I/usr/include/ruby-1.9.1 -I. -I/usr/
> lib/ruby/gems/1.9.1/gems/ffi-1.0.7/ext/ffi_c/libffi/include -
> DRUBY_EXTCONF_H=\"extconf.h\"  -D_FILE_OFFSET_BITS=64  -fPIC -O2 -
> march=pentium-m -pipe -mno-tls-direct-seg-refs -fno-strict-aliasing -
> fPIC -Wno-declaration-after-statement   -o LastError.o -c LastError.c
> i686-pc-linux-gnu-gcc -shared -o ffi_c.so ClosurePool.o
> DynamicLibrary.o Platform.o ffi.o Thread.o MethodHandle.o
> StructLayout.o FunctionInfo.o Buffer.o StructByValue.o Variadic.o
> DataConverter.o ArrayType.o MappedType.o Struct.o Function.o Pointer.o
> Type.o Call.o MemoryPointer.o StructByReference.o AbstractMemory.o
> Types.o LastError.o -L. -L/usr/lib -Wl,-R/usr/lib -L. -Wl,-O1,--hash-
> style=gnu -rdynamic -Wl,-export-dynamic -Wl,--no-undefined   /usr/lib/
> ruby/gems/1.9.1/gems/ffi-1.0.7/ext/ffi_c/libffi/.libs/
> libffi_convenience.a -Wl,-R -Wl,/usr/lib -L/usr/lib -lruby19  -
> lpthread -lrt -ldl -lcrypt -lm   -lc
> AbstractMemory.o: In function `memory_get_array_of_ulong':
> AbstractMemory.c:(.text+0x40c9): undefined reference to
> `__builtin_bswap32'
> AbstractMemory.o: In function `memory_put_array_of_ulong':
> AbstractMemory.c:(.text+0x425c): undefined reference to
> `__builtin_bswap32'
> <snip>

You are probably best off contacting engineyard support for help.

cr