From: deivid via ruby-core <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: deivid <noreply@ruby-lang.org>
Subject: [ruby-core:119491] [Ruby master Bug#20791] RbCONFIG::CONFIG does not have a LIBRUBY_RELATIVE key on mswin
Date: Wed, 09 Oct 2024 10:22:29 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-20791.20241009102228.7174@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20791.20241009102228.7174@ruby-lang.org>
Issue #20791 has been reported by deivid (David Rodríguez).
----------------------------------------
Bug #20791: RbCONFIG::CONFIG does not have a LIBRUBY_RELATIVE key on mswin
https://bugs.ruby-lang.org/issues/20791
* Author: deivid (David Rodríguez)
* Status: Open
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
I noticed that mswin Ruby does not provide `RbCONFIG::CONFIG["LIBRUBY_RELATIVE"]`. My understanding is that all Windows should have this set to "yes", as per https://github.com/ruby/ruby/blob/67d6e89b0b6d7dd7d6454ace7734157ee51f3f79/configure.ac#L3690-L3692.
Since `rbinstall` script uses this config to decide whether binstubs need a bash prolog or not as per https://github.com/ruby/ruby/blob/67d6e89b0b6d7dd7d6454ace7734157ee51f3f79/tool/rbinstall.rb#L418-L426, I think mswin is getting incorrect binstubs generated by default.
I tried to look briefly into why this happens, but I could not figure it out.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
next parent reply other threads:[~2024-10-09 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 10:22 deivid via ruby-core [this message]
2024-10-09 12:35 ` [ruby-core:119492] " deivid via ruby-core
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=redmine.issue-20791.20241009102228.7174@ruby-lang.org \
--to=ruby-core@ml.ruby-lang.org \
--cc=noreply@ruby-lang.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).