Hmmm I wonder if rubygems uses something which requires this only on a
particular type of gemspec? Just random flung out suggestion :)
-Tom
On Fri, Dec 6, 2013 at 3:14 AM, Christian MICHON wrote:
> Still trying to figure out the env difference, to no avail yet.
>
> I've done more tests, and a
Still trying to figure out the env difference, to no avail yet.
I've done more tests, and apparently some rubygems work if included in the
jar file: I'll add pry-rescue to figure out the exact location of the
failure, as the backtrace if quite limited.
Any other idea to debug this?
On Thu, Dec
Yeah I can see that there is an issue here. No doubt it is something that
2.1 support pulled in that we probably are doing differently in DL. So
that is definitely a bug and an issue on DL not working makes sense. I can
confirm that Fiddle::Pointer does not exist. In fact, looking at 1.9
versio
Hi Tom.
Well, my environment is as naked as possible (jdk 1.7.0_45-b18 64 bits, no
GEM_PATH set, etc... but I do have an IRBRC)
Could you please try this in your env?
jruby -S jirb
>> require 'dl'
=> true
>> require 'fiddle'
=> true
>> DL.fiddle?
=> true
>> Fiddle::Pointer
NameError: uninitializ
We are now tracking issues on github. The Jira ones are still there but
mostly for posterity. Open new ones on github.
I am not seeing this error:
java -jar ~/Downloads/jruby-complete-9000.dev.jar -S jgem list
I get am empty GEM list but no error. A dev build also shows no issue.
Either my en
Hi,
I've downloaded
http://ci.jruby.org/snapshots/master/jruby-complete-9000.dev.jar and I'm
trying to test out current state of dev of jruby 9k on Windows 7
"jruby -v" works out of the box:
jruby 9000.dev (2.1.0.dev) 2013-12-04 e68098b on Java HotSpot(TM) 64-Bit
Server VM 1.7.0_45-b18 [Windows 7
