Repository navigation
fix gap - #6752
fix gap#6752
Conversation
|
passagemath-gap test says I guess that this is not the gap's issue. |
Something seems to be broken with python tests. Investigating... |
|
The issue with the python tests is fixed now, if you'd like to test |
This generally indicates that |
But fwasm is not compatible with asyncify, which is required by gap's garbage collecting mechanism. |
IsabelParedes
left a comment
There was a problem hiding this comment.
Since the changes to gap break passagemath-gap, I would like to get @mkoeppe opinion before merging.
Thank you!
|
Is it possible for the passagemath-gap test to work without -fwasm? |
Unfortunately I don't understand the constraints of this platform well enough to comment... What's going on in the dynamic linking of the Python modules that is failing here, and why is dynamic linking otherwise generally avoided in the emscripten-forge recipes? |
invoke_viii should be relevant to the JavaScript-based exception handling (-fexceptions). Most of the recipe here is built with WebAssembly-based exception handling (-fwasm). That should be the reason for failing. However, gap relies on asyncify flag which is not compatible with -fwasm. |
IsabelParedes
left a comment
There was a problem hiding this comment.
Thank you!
If this causes issues for passagemath-gap, we can pin it to a previous build or split the gap package as needed.
|
Claude suggested splitting gap recipe to build libgap.a without ASYNCIFY. passagemath-gap only need libgap.a right? @mkoeppe |
|
No, it needs all of GAP, except for the executable program. |
|
That is a problem. The pkg dir of gap is 1GB size large. Even after gzip it is still 500MB. GitHub will not allow hosting such large file in pages. |
|
To clarify, of course it does not need all GAP packages up front. |

Template B: Checklist for updating a package
PR Formatting
Add [package-name]orUpdate [package-name] to [version]Package Details
Build Notes