Charles Oliver Nutter

Well, io-console on JRuby is the one I can think of offhand, since I saw the warnings earlier today. The key line there is this: ``` File.write("Makefile", dummy_makefile($srcdir).join("")) ``` Where...

`bindex` is another gem that I believe optionally builds its extension, and I have seen warnings about it as well.

@deivid-rodriguez Another example of this appears to be related to RVM, but I am not clear who is really at fault. The message comes from RG, but may be triggered...

Hey I think this might be reproducible using a build from JRuby master (or possibly a JRuby 9.2.x build with latest RG) this way: * gem install jruby-launcher, which builds...

Poking this one again... I still do not have simple steps to reproduce, but I am not the only one who has seen this. It may be due to using...

@deivid-rodriguez Is there some marker used to indicate whether an extension has been built? In my case, most of the libraries that produce this warning do not have extensions at...

I believe this is the problem. Some gems ship both the C extension and the Java extension (or pure-Ruby code for JRuby) in the same package. When installing on JRuby,...

I believe I have figured out the problem and would like to reopen this and work on a solution. The problem is that when a gem has a JRuby extension...

When a gem specifies that it has an extension, the makefile will always be run. In this case, both the C extensions and the JRuby jar are shipped in the...

> shipping a separate gem for JRuby is the correct way > I think io-console is already doing That's because I did that one and because having JRuby bits in...