diff options
author | Alan Wu <XrXr@users.noreply.github.com> | 2023-04-20 09:44:02 -0400 |
---|---|---|
committer | Alan Wu <XrXr@users.noreply.github.com> | 2023-04-26 15:02:23 -0400 |
commit | adaff1fc496b6f01fb1c4c812b9b4082618e2f79 (patch) | |
tree | 453d043ffdae6210a561ca7966b5c4783127f6f7 /vm.c | |
parent | 92466e440d459cd21e89f8bfbe6d8438bcaa9389 (diff) | |
download | ruby-adaff1fc496b6f01fb1c4c812b9b4082618e2f79.tar.gz |
[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"
Diffstat (limited to 'vm.c')
-rw-r--r-- | vm.c | 3 |
1 files changed, 0 insertions, 3 deletions
@@ -4037,9 +4037,6 @@ Init_vm_objects(void) vm->mark_object_ary = rb_ary_hidden_new(128); vm->loading_table = st_init_strtable(); vm->frozen_strings = st_init_table_with_size(&rb_fstring_hash_type, 10000); -#if EXTSTATIC - vm->static_ext_inits = st_init_strtable(); -#endif } /* Stub for builtin function when not building YJIT units*/ |