diff options
| author | nagachika <nagachika@ruby-lang.org> | 2024-04-07 14:41:29 +0900 |
|---|---|---|
| committer | nagachika <nagachika@ruby-lang.org> | 2024-04-07 14:41:29 +0900 |
| commit | baa5bc16c17e3b4dac7b590ed5d6b7e705535e15 (patch) | |
| tree | 38435092bb7f66e26427188bdb8ee25a783f9e35 /spec/ruby/core/basicobject | |
| parent | 27606daf8efeb0ae6d0590a2c9bb1c5aae07f140 (diff) | |
merge revision(s) adaff1fc496b6f01fb1c4c812b9b4082618e2f79: [Backport #19592]
[Bug #19592] Fix ext/Setup support
After [1], using ext/Setup to link some, but not all extensions failed
during linking. I did not know about this option, and had assumed that
only `--with-static-linked-ext` builds can include statically linked
extensions.
Include the support code for statically linked extensions in all
configurations like before [1]. Initialize the table lazily to minimize
footprint on builds that have no statically linked extensions.
[1]: 790cf4b6d0475614afb127b416e87cfa39044d67 "Fix autoload status of
statically linked extensions"
---
load.c | 28 +++++++++++++++++-----------
vm.c | 3 ---
vm_core.h | 6 ------
3 files changed, 17 insertions(+), 20 deletions(-)
Diffstat (limited to 'spec/ruby/core/basicobject')
0 files changed, 0 insertions, 0 deletions