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_core.h | |
| 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_core.h')
| -rw-r--r-- | vm_core.h | 6 |
1 files changed, 0 insertions, 6 deletions
@@ -557,10 +557,6 @@ struct rb_iseq_struct { #define ISEQ_BODY(iseq) ((iseq)->body) -#ifndef EXTSTATIC -#define EXTSTATIC 0 -#endif - #ifndef USE_LAZY_LOAD #define USE_LAZY_LOAD 0 #endif @@ -686,11 +682,9 @@ typedef struct rb_vm_struct { VALUE loaded_features_realpath_map; struct st_table *loaded_features_index; struct st_table *loading_table; -#if EXTSTATIC // For running the init function of statically linked // extensions when they are loaded struct st_table *static_ext_inits; -#endif /* signal */ struct { |