From: "k0kubun (Takashi Kokubun) via ruby-core" Date: 2022-12-27T21:45:08+00:00 Subject: [ruby-core:111463] [Ruby master Bug#19271] irb ignores rbs and debug Issue #19271 has been updated by k0kubun (Takashi Kokubun). Subject changed from irb ignores rbs and debug with YJIT enabled to irb ignores rbs and debug Description updated Assignee set to hsbt (Hiroshi SHIBATA) ruby -v changed from ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [arm64-darwin21] to ruby 3.2.0 (2022-12-25 revision a528908271) [arm64-darwin22] YJIT or `RUBY_YJIT_ENABLE=1` doesn't interfere with that process, and I confirmed that this is reproducible without YJIT as @st0012 did. So removing the reference to YJIT from the ticket description, also fixing `ruby -v` as you said. ``` $ rm -rf /opt/rubies/3.2.0 $ rm -rf ~/.gem $ ruby-install 3.2.0 $ /opt/rubies/3.2.0/bin/irb Ignoring debug-1.6.3 because its extensions are not built. Try: gem pristine debug --version 1.6.3 Ignoring rbs-2.7.0 because its extensions are not built. Try: gem pristine rbs --version 2.7.0 irb(main)[01:0]> ``` I recall @hsbt said he'll investigate the issue that those warning messages are printed, so I'll send this to his way. ---------------------------------------- Bug #19271: irb ignores rbs and debug https://bugs.ruby-lang.org/issues/19271#change-100834 * Author: olivierlacan (Olivier Lacan) * Status: Open * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) * ruby -v: ruby 3.2.0 (2022-12-25 revision a528908271) [arm64-darwin22] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- Not sure this is a serious issue but when starting IRB this (potentially confusing) message is immediately printed: ``` $ irb Ignoring debug-1.7.1 because its extensions are not built. Try: gem pristine debug --version 1.7.1 Ignoring rbs-2.8.2 because its extensions are not built. Try: gem pristine rbs --version 2.8.2 irb(main):001:0> ``` This is on a fresh installation of Ruby 3.2.0 with an empty Gemfile in the directory. I haven't run gem pristine on any gem since I hadn't installed any gems after installing Ruby 3.2.0 here but FYI: ``` $ gem list | grep "rbs\|debug" debug (1.7.1) rbs (2.8.2) ``` This seems to suggest that C extensions weren't built for those gems when they were installed during the Ruby installation process. Just to be safe I checked and while I do use rbenv and ruby-build to compile and manage Rubies, I don't have a default gem installer set up so as far as I know these gems weren't installed by my system. -- 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/postorius/lists/ruby-core.ml.ruby-lang.org/