Ruby gems are not found after successful install

[darabi]

I would like to use ruby gem nokogiri with MetaCall (installed with install.sh) and am using the repo metacall/express-faas-rpc-example as a starting point.

I added a corresponding Gemfile, called metacall bundler install which reports the gem as being present.

When I add the `require 'nokogiri' statement to mult.rb, I get

Loading... mult.rb
Error: Ruby module evaluation failed
#<LoadError: cannot load such file -- nokogiri>
(eval):1:in `require'
(eval):1:in `<main>'
Error: Invalid ruby module loading /wrk/metacall/express-faas-rpc-example/scripts/mult.rb
Error: No module could be loaded
Error: Handle (nil) passed to metacall_handle_export is not valid
NodeJS Loader Error: MetaCall could not load from file

@viferga mentioned in the Discord chat that this is related to some environment variables and to #5.

[viferga]

@darabi Even when adding the env vars:

distributable-linux/source/metacall.scm

Line 482 in 5eb042f

; Ruby

It seems ruby is totally fucked. I could not make ruby find the gems installed by bundler, and other gems fail horribly like the ones I have added in the test.

If you are more experienced than me with Ruby, you can try to debug it: 5eb042f

It would be also interesting to report this to Guix team.

[shaggyyy2002]

@darabi try updating the ruby to v3 or latest stable release. that should solve your problem. Have faced the problem too.
for more you could check this out: https://nokogiri.org/tutorials/installing_nokogiri.html

[viferga]

@shaggyyy2002 it's still happening but now you can use metacall from ruby executable, this should use your own ruby installation and it will mitigate this problem, you do not need metacall CLI to execute code that mixes languages.

@darabi you may be interested on this ^

[viferga]

@darabi @shaggyyy2002 I have done some changes with this in the core, I think we should try again, it may be solved now. I am debugging other things in windows meanwhile but the next step will be checking those changes. Also now there is another improvement which is that now you can use your ruby installation by default instead of metacall, so this is another workaround to the problem.

The gem is still not published but I will be publishing it soon too. You can use it directly as metacall.rb from the core source if you need it, inside source/ports/rb_port.