[#111712] [Ruby master Feature#19322] Support spawning "private" child processes — "kjtsanaktsidis (KJ Tsanaktsidis) via ruby-core" <ruby-core@...>
SXNzdWUgIzE5MzIyIGhhcyBiZWVuIHJlcG9ydGVkIGJ5IGtqdHNhbmFrdHNpZGlzIChLSiBUc2Fu
14 messages
2023/01/07
[ruby-core:111626] [Ruby master Bug#19275] Bundled gems extensions are not installed with 3.2.0 release tarball
From:
"xtkoba (Tee KOBAYASHI) via ruby-core" <ruby-core@...>
Date:
2023-01-04 15:57:35 UTC
List:
ruby-core #111626
Issue #19275 has been updated by xtkoba (Tee KOBAYASHI).
Here it is:
```
rm -f ./.bundle/specifications/debug-1.7.1.gemspec
rm -f ./.bundle/specifications/rbs-2.8.2.gemspec
rm -rf ./.bundle/gems/debug-1.7.1/
rm -rf ./.bundle/gems/rbs-2.8.2/
rm -f .bundle/specifications/debug-1.7.1.gemspec
rm -f .bundle/specifications/rbs-2.8.2.gemspec
rm -rf .bundle/gems/debug-1.7.1/
rm -rf .bundle/gems/rbs-2.8.2/
```
This is the output of
```bash
ruby ${top_srcdir}/tool/outdate-bundled-gems.rb -n .
```
invoked right before or right after `make install`, where `top_srcdir` denotes the root of the source tree.
----------------------------------------
Bug #19275: Bundled gems extensions are not installed with 3.2.0 release tarball
https://bugs.ruby-lang.org/issues/19275#change-100997
* 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/
______________________________________________
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/