Using gem compiler in a restricted server environment about gem-compiler HOT 4 CLOSED

Hello @rgiessmann, apologies for the delayed response. I thought left a comment when assigning the question label, but seems forgot to submit 🤦‍♂️

Do you intended gem-compiler to work for such a scenario, or am I misled?

Yes and no. gem-compiler was created to work to remove the need of having a compiler available on the final machines, but you need to have certain control on OS or the version of Ruby. In your case, you have none of the later, so aiming to produce a 100% reproducible environment might be a challenge.

Do you have an idea on this, or could you provide me with a "this is how we usually do it"-strategy?

My recommendation on this will be a deeper analysis of the Ruby installation they provide and be able to mimic as much as possible their options.

If libruby.so.2.4 is failing to load msgpack.so, it might linking to other shared objects that might be missing on the target platform.

I will recommend mimic as much as possible the exact version of Ruby that is installed in the remote, including the build options.

Given the limited SSH access you have, try to use the following commands:

Obtain the configure options that were used to build Ruby:

$ ruby -v -e 'puts RbConfig::CONFIG["configure_args"]'

This should provide you the options to be used when building your version of Ruby in your copy of the environment. Options like --enable-shared and --enable-load-relative have an important role when trying to load extensions that were produced by a non-similar environment.

Try to use the same options when compiling the version of Ruby you're using to generate the binary gems.

Also, try to determine the versions/libraries libruby.so.2.4 links to, and confirm the ones of msgpack.so too, using ldd (if available)

$ ldd /var/www/vhosts/hosting116285.a2f45.netcup.net/test.gcsb.info/vendor/bundle/ruby/2.4.0/gems/msgpack-1.2.6-x86_64-linux/lib/msgpack/msgpack.so

$ ldd /path/to/libruby.so.2.4

Since I don't know more details of your ruby installation, check if configure_args showed a --prefix option and inspect a relative lib directory that might include the respective .so file.

You might also look for libruby.so.2.4 by using ldd over the ruby interpreter in use. Use which ruby to determine the location and then use ldd on it, example:

$ ldd ~/.asdf/installs/ruby/2.5.1/bin/ruby
        linux-vdso.so.1 =>  (0x00007fffeda03000)
        libruby.so.2.5 => /home/luis/.asdf/installs/ruby/2.5.1/bin/../lib/libruby.so.2.5 (0x00007f41b62f4000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f41b5f20000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f41b5d00000)
        libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x00007f41b5a70000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f41b5860000)
        libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007f41b5620000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f41b5300000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f41b6a00000)

Let me know if these help you.

Cheers.

from gem-compiler.

Hello @rgiessmann, didn't receive a follow up from your end.

Please let me know if you're still interested into explore this or have additional questions.

Cheers.

from gem-compiler.

Hello @rgiessmann, doing a follow up on this. Are you still experiencing this issue? Were you able to explore my previous comments?

Please let me know.

Cheers.

from gem-compiler.

Hello @rgiessmann, closing this due inactivity.

Please let us know if you're still impacted by this and can provide more details.

Cheers.

from gem-compiler.