Florian Ebeling

`mkmf` is polluting the toplevel namespace [here](https://github.com/ruby/ruby/blob/trunk/lib/mkmf.rb#L2731) with it's defintion of [find_type](https://github.com/ruby/ruby/blob/trunk/lib/mkmf.rb#L1240). And `ffi` is tripping over it [here](https://github.com/ffi/ffi/blob/master/lib/ffi/struct.rb#L332).

Yes, the right fix would be to isolate mkmf cleanly into a module. But FFI is also a bit casual about grabbing any `find_type` it sees and calling it. For...

Yes, it looks like a welcome workaround for anyone who's blocked by this problem. It also neatly fits the description you gave a few days back - good job :)...

I think there's another way to achieve the same thing, via the primary key: ```elixir insert(:user, id: 1337) build(:comment, user: nil, user_id: 1337) |> insert() ``` I imagine it would...

I don't have access to a Windows machine, so I can't really help. Patches would be welcome.

This package, rb-libsvm, doesn't support Windows, unfortunately (unless somebody supplies a patch). Please note that libsvm-ruby-swig and rb-libsvm packages are alternatives and not meant to be used together.

Just saw that rake-compiler has support for cross-compiling now, and also provides a special `rake-compiler-dev-box` VM for this. Might make implementing this thing easier. https://github.com/rake-compiler/rake-compiler#cross-compilation---the-future-is-now

I don't find the time to do this. So the new status pretty much is: PR welcome.

@Kraviscloud What is gp?

@mipearson - yes, you're right. This only works with the dev server running a the next, or pre-compiling. Sorry, I didn't really minimize this. It did help me in a...