also printing the path to the actual file that failed to load would be useful, if that's possible.

This has come up for us a few more times since I opened it. We're currently giving users info about the -Djava.io.tmpdir workaround, but that makes me a little leery because I believe it means that any other temp files that the process writes during its lifetime will also be written to that directory, which is bad.

I think it might be worth adding a jruby-ffi-specific config setting that could be used to define the temp location that would be used only for these files that need to be executable, and that way we wouldn't have to override the global temp dir.

This is probably a requirement of Java. That error message us related to the POSIX features which use a Java based FFI package (related to JRubys) not the ruby FFI package. it would appear you have to turn off the native features or provide Java with a place to put temporary files.