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.
Related issues
Bug #19592: Unable to statically link a single extension in 3.2.x and >=3.1.4
Added by alanwu (Alan Wu) over 2 years ago
[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-extbuilds can include statically linkedextensions.
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.