From: Brett Gilio <brettg@posteo.net>
To: Vicente Eduardo <vic798@gmail.com>
Cc: 38500@debbugs.gnu.org
Subject: bug#38500: Ruby is built against libruby-static.a
Date: Sat, 07 Dec 2019 10:44:38 -0600 [thread overview]
Message-ID: <87fthwdr0p.fsf@posteo.net> (raw)
In-Reply-To: <CAOUKKgE=KutdNR2KTFeAme_8qPoq9khx_9kroTFRFZwPUAiYUg@mail.gmail.com> (Vicente Eduardo's message of "Thu, 5 Dec 2019 14:25:51 +0100")
Vicente Eduardo <vic798@gmail.com> 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 interpreters?
This is a prevalent issue not just for Ruby, but for also how we handle
GHC, Rust, JDK, and so on.
Generally, I think we dynamically link most objects. _BUT_, I could be
missing part of the story here. So I am going to wait for the higher
powers that be to respond.
In the mean time, when I get a moment, I will do some auditing on this
package to see if the issue is just that we are missing some compilation
procedure. Hopefully it is just as simple as that, but I still think the
issue of linkage style (dynamic vs static linkage) remains prevalent.
Hopefully we hear some noise on this soon.
--
Brett M. Gilio
https://git.sr.ht/~brettgilio/
next prev parent reply other threads:[~2019-12-08 3:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 13:25 bug#38500: Ruby is built against libruby-static.a Vicente Eduardo
2019-12-07 16:44 ` Brett Gilio [this message]
2019-12-08 14:44 ` Vicente Eduardo
2019-12-08 14:49 ` Vicente Eduardo
2019-12-08 15:42 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-12-09 18:33 ` Brett Gilio
2019-12-09 20:57 ` Brett Gilio
2019-12-13 3:51 ` Brett Gilio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fthwdr0p.fsf@posteo.net \
--to=brettg@posteo.net \
--cc=38500@debbugs.gnu.org \
--cc=vic798@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.