Skip to content
This repository

Missing FFI constant prevents loading ffi-proj4 #2095

Closed
sempervictus opened this Issue December 10, 2012 · 1 comment

2 participants

RageLtMan Brian Shirai
RageLtMan

This seems related to fde9474, but a bit less pleasant. FFI 1.2.0 implements a number of additional Platform constants such as IS_BSD...

The trace:

require 'ffi-proj4'
NameError: Missing or uninitialized constant: FFI::Platform::IS_MAC
from kernel/common/module.rb:472:in const_missing'
from /usr/local/rvm/gems/rbx-head@testing/gems/cb-ffi-proj4-0.0.8/lib/ffi-proj4.rb:32:in
proj4_library_path'
from /usr/local/rvm/gems/rbx-head@testing/gems/cb-ffi-proj4-0.0.8/lib/ffi-proj4.rb:56:in __module_init__ (FFIProj4)'
from /usr/local/rvm/gems/rbx-head@testing/gems/cb-ffi-proj4-0.0.8/lib/ffi-proj4.rb:22:in
module_init (Proj4)'
from /usr/local/rvm/gems/rbx-head@testing/gems/cb-ffi-proj4-0.0.8/lib/ffi-proj4.rb:10:in __script__'
from kernel/common/codeloader.rb:212:in
require'
from kernel/common/kernel.rb:648:in gem_original_require (require)'
from /usr/local/rvm/rubies/rbx-head/lib/rubygems/custom_require.rb:60:in
require'
from (irb):2
from kernel/common/block_environment.rb:75:in call_on_instance'
from kernel/common/eval.rb:75:in
eval'
from kernel/common/kernel19.rb:42:in loop'
from kernel/common/throw_catch19.rb:8:in
catch'
from kernel/common/throw_catch.rb:10:in register'
from kernel/common/throw_catch19.rb:7:in
catch'
from kernel/common/throw_catch19.rb:8:in catch'
from kernel/common/throw_catch.rb:10:in
register'
from kernel/common/throw_catch19.rb:7:in catch'
from kernel/delta/codeloader.rb:68:in
load_script'
from kernel/delta/codeloader.rb:118:in load_script'
from kernel/loader.rb:615:in
script'
from kernel/loader.rb:816:in `main'

Brian Shirai brixen closed this January 08, 2013
Brian Shirai
Owner

We now bundle a 1.2.0 version of the FFI gem, however, there is a bug in RVM that omits the pre-installed gems. So if using RVM, use the recently released 1.3.0 FFI gem which builds correctly on Rubinius.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.