Repository navigation
Compilation is broken with HAVE_DYNAMIC_LOADING=0 #122907
Copy link
Copy link
Closed
Labels
3.13only security fixesonly security fixes3.14bugs and security fixesbugs and security fixesOS-emscriptentopic-importlibtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Description
Activity
- addedtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
on Aug 11, 2024 I'll take a look.
Is this for Emscripten of WASI? If it's for the former it's no longer officially supported as of CPython 3.13 (code for Emsripten will start being removed in CPython 3.14/main, I just haven't gotten around to doing the removal).
- added3.13only security fixesonly security fixes3.14bugs and security fixesbugs and security fixesand removed
on Aug 12, 2024 The problem manifests with
HAVE_DYNAMIC_LOADINGnot set, regardless of any WASM-related build. I'll get builds without dynamic loading working again with a minimal change, but there are broader deficiencies to address. See gh-122950.Doing some triaging. Is this all good to close?
- Reacted by Peter Bierma and João Matos
Metadata
Metadata
Assignees
Labels
3.13only security fixesonly security fixes3.14bugs and security fixesbugs and security fixesOS-emscriptentopic-importlibtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Bug report
Bug description:
When compiling for Wasm with
--disable-wasm-dynamic-linking, we end up withHAVE_DYNAMIC_LOADING=0, which is currently broken with the following linking errors:I believe its a regression introduced in 529a160.
@ericsnowcurrently, would you be able to take a look into fixing this?
CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux
Linked PRs