Issue #19275 has been updated by hsbt (Hiroshi SHIBATA). I could reproduce this with BASERUBY and fresh install with tarball. `tool/outdate-bundled-gems.rb` will removing `debug.so` and `rbs_extension.so` while `make install`. ---------------------------------------- Bug #19275: Bundled gems extensions are not installed with 3.2.0 release tarball https://bugs.ruby-lang.org/issues/19275#change-101016 * Author: xtkoba (Tee KOBAYASHI) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) * ruby -v: ruby 3.2.0 (2022-12-25 revision a528908271) [aarch64-linux-android] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- Bundled gems extensions are not installed with 3.2.0 release tarball when cross building for `aarch64-linux-android` target. Possibly related to #19271. Excerpt from build log: ``` 2022-12-28T12:39:39.5065133Z linking shared-object rbs_extension.so 2022-12-28T12:39:39.5317220Z Successfully remade target file '../../../../../.bundle/extensions/aarch64-linux-android/3.2.0/rbs-2.8.2/rbs_extension.so'. [...] 2022-12-28T12:40:06.9333744Z rm -rf .bundle/extensions/aarch64-linux-android/ ``` Seems like bundled gems extensions are built but removed afterwards. The workaround we took is to patch `common.mk` so that `outdate-bundled-gems` is not triggered: ```patch --- a/common.mk +++ b/common.mk @@ -1375,7 +1375,6 @@ refresh-gems: update-bundled_gems prepare-gems prepare-gems: $(HAVE_BASERUBY:yes=update-gems) $(HAVE_BASERUBY:yes=extract-gems) -prepare-gems: $(DOT_WAIT) $(HAVE_BASERUBY:yes=outdate-bundled-gems) extract-gems: $(HAVE_BASERUBY:yes=update-gems) update-gems$(gnumake:yes=-sequential): PHONY ``` Full build log is attached. ---Files-------------------------------- build.log.xz (245 KB) -- https://bugs.ruby-lang.org/