From: "hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "hsbt (Hiroshi SHIBATA)" <noreply@ruby-lang.org>
Subject: [ruby-core:119648] [Ruby master Bug#20854] Some bundled gems are not installed starting with 007c75ce4c66243e41144c6977e5ccbf4ab71c93
Date: Thu, 31 Oct 2024 07:21:01 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-110303.20241031072101.54590@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20854.20241030224225.54590@ruby-lang.org>
Issue #20854 has been updated by hsbt (Hiroshi SHIBATA).
Status changed from Open to Assigned
Assignee set to hsbt (Hiroshi SHIBATA)
----------------------------------------
Bug #20854: Some bundled gems are not installed starting with 007c75ce4c66243e41144c6977e5ccbf4ab71c93
https://bugs.ruby-lang.org/issues/20854#change-110303
* Author: jvreeland (Justin Vreeland)
* Status: Assigned
* Assignee: hsbt (Hiroshi SHIBATA)
* ruby -v: Building ruby from master
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
I noticed in ruby 3.4.0 preview 2 that some bundled gems weren't being installed any more. I'm running in the same environment each time and bundled gems are installed fine with 3.3 or with the mentioned commit reverted.
I bisected this from a version that did install the gems to commit:007c75ce4c66243e41144c6977e5ccbf4ab71c93 . The comment in that commit does indicate that it's mean to skip games if the gems are not found or can't be built but the final message is 'not found in bundled_gems'. I'm unsure if this is this is working as intended.
When my build finishes I see the following line in the log:
```
installing bundled gem cache: /home/user/ruby/build/.rubies/bisect/lib/ruby/gems/3.4.0+0/cache
skipped bundled gems:
bigdecimal-3.1.8.gem not found in bundled_gems
debug-1.9.2.gem not found in bundled_gems
nkf-0.2.0.gem not found in bundled_gems/rac
racc-1.8.1.gem not found in bundled_gems
rbs-3.6.1.gem not found in bundled_gems
syslog-0.1.2.gem not found in bundled_gems
typeprof-0.30.0.gem not found in bundled_gems
```
I see racc in bundled gems and cached in downloads.
I don't see any files named gem.build_complete or errors concerning gem building or missing C extensions in my build logs. Is there additional configure flags or dependencies I need to include the bundled gems in the upcoming 3.4.0 ruby release?
I followed the instructions at: https://docs.ruby-lang.org/en/master/contributing/building_ruby_md.html to build:
```
git clean -dxf
git checkout -f
autoreconf -fi
mkdir build
pushd build
../configure --prefix=(pwd)/.rubies/bisect
make -j(nproc)
make install
popd
find build/.rubies/bisect -name 'racc' | grep .
```
--
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 prev parent reply other threads:[~2024-10-31 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 22:42 [ruby-core:119645] " jvreeland (Justin Vreeland) via ruby-core
2024-10-31 7:21 ` hsbt (Hiroshi SHIBATA) via ruby-core [this message]
2025-06-04 7:51 ` [ruby-core:122407] [Ruby " hsbt (Hiroshi SHIBATA) 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.journal-110303.20241031072101.54590@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).