Pushed to core-updates with fd248cb815d571043c3a0c52a01c9b3e368a069e.
Closing
--
Brett M. Gilio
Homepage -- https://scm.pw/
GNU Guix -- https://guix.gnu.org/
I have submitted a patch that will go into core-updates, with bug report
#38552. That patch will close both of these bug reports.
Thanks.
--
Brett M. Gilio
https://git.sr.ht/~brettgilio/
Tobias Geerinckx-Rice writes:
> You could ask Pjotr Prins and David Thompson but I suspect that it was
> simply an oversight: most packages link dynamically by default because
> it's the sane thing to do, and it would have been reasonable to assume
> Ruby did too.
Tobias,
I did some investigatin
Vincente, Brett,
Brett Gilio 写道：
Vicente Eduardo writes:
I would like to have two versions, or at least the dynamic one,
that's the common way
Ruby should be built, and also the Guixy style.
Important: static linking isn't the Guixy style at all!
Statically linking different packages ‘sub
I have checked the flags needed for compiling dynamically.
It should be very easy to solve, just by adding this flag to the configure:
--enable-shared
This should be enough to compile Ruby runtime dynamic library and to
compile Ruby interpeter executable against this lib.
Reference:
https://git
Python and Ruby link dynamically by default from the executable of the
runtime to the runtime library. Most runtimes do that, it is a good design
that allows reusing the runtime to the embedders. As exception of NodeJS
which avoids this because of a design decision related to the distribution,
and
Vicente Eduardo writes:
> I would like to have two versions, or at least the dynamic one, that's the
> common way
> Ruby should be built, and also the Guixy style.
This actually brings up a rather interesting point. What is the Guix
protocol on compilation for dynamic vs statically linked inter
I'm trying to use Ruby interpeter as a library to link it against my
project (metacall:
https://github.com/metacall/distributable/blob/65493b393388f5d66d9b466e5d49f9128fee27ea/source/metacall.scm#L117
). So I tried to download the Ruby package and libruby.so seems not to be
present.
Running ldd ag
