ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
* [ruby-core:119491] [Ruby master Bug#20791] RbCONFIG::CONFIG does not have a LIBRUBY_RELATIVE key on mswin
@ 2024-10-09 10:22 deivid via ruby-core
  2024-10-09 12:35 ` [ruby-core:119492] " deivid via ruby-core
  0 siblings, 1 reply; 2+ messages in thread
From: deivid via ruby-core @ 2024-10-09 10:22 UTC (permalink / raw)
  To: ruby-core; +Cc: deivid

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/

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [ruby-core:119492] [Ruby master Bug#20791] RbCONFIG::CONFIG does not have a LIBRUBY_RELATIVE key on mswin
  2024-10-09 10:22 [ruby-core:119491] [Ruby master Bug#20791] RbCONFIG::CONFIG does not have a LIBRUBY_RELATIVE key on mswin deivid via ruby-core
@ 2024-10-09 12:35 ` deivid via ruby-core
  0 siblings, 0 replies; 2+ messages in thread
From: deivid via ruby-core @ 2024-10-09 12:35 UTC (permalink / raw)
  To: ruby-core; +Cc: deivid

Issue #20791 has been updated by deivid (David Rodríguez).


Thank you @nobu!

----------------------------------------
Bug #20791: RbCONFIG::CONFIG does not have a LIBRUBY_RELATIVE key on mswin
https://bugs.ruby-lang.org/issues/20791#change-110106

* Author: deivid (David Rodríguez)
* Status: Closed
* 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/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-10-09 12:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-10-09 10:22 [ruby-core:119491] [Ruby master Bug#20791] RbCONFIG::CONFIG does not have a LIBRUBY_RELATIVE key on mswin deivid via ruby-core
2024-10-09 12:35 ` [ruby-core:119492] " deivid via ruby-core

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).