RuntimeError: ECL says: Module error: Don't know how to REQUIRE MAXIMA #9
Comments
|
@embray I know close to nothing about ecl and maxima. Any ideas? |
|
Upgrading to 16.1.3 fixes that issue (but causes lots of others.) |
saraedum
added a commit
to saraedum/maxima-feedstock
that referenced
this issue
Sep 4, 2018
Sage 8.3 runs into trouble with ecl 16.1.3 and to require maxima from within Sage, we need to build and run maxima with the same version it seems. Fixes conda-forge#9; see also conda-forge/sagelib-feedstock#19.
saraedum
added a commit
to saraedum/maxima-feedstock
that referenced
this issue
Sep 4, 2018
Sage 8.3 runs into trouble with ecl 16.1.3 and to require maxima from within Sage, we need to build and run maxima with the same version it seems. Fixes conda-forge#9; see also conda-forge/sagelib-feedstock#19.
saraedum
added a commit
to saraedum/maxima-feedstock
that referenced
this issue
Sep 4, 2018
Sage 8.3 runs into trouble with ecl 16.1.3 and to require maxima from within Sage, we need to build and run maxima with the same version it seems. Fixes conda-forge#9; see also conda-forge/sagelib-feedstock#19.
Ah, the song of our people :( |
|
I still have yet to actually try building Sage in conda. If I try to follow the instructions to do that now, will I reproduce the issue? If so then I can proceed to investigate (6.1.2 is an awfully precise pinning, which is unfortunate, and strange since I've usually found ECL to be pretty stable...) |
|
I'm still not very familiar with working with conda builds (at least these days--it's changed a lot since I last played with it). It's not clear to me what the most effective procedure is for testing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At https://github.com/conda-forge/sage-feedstock we are now seeing lots of
RuntimeError: ECL says: Module error: Don't know how to REQUIRE MAXIMA.Do we need to pin ecl more strictly, i.e., use the same version when running maxima that we used to build maxima? Or is this something else?The text was updated successfully, but these errors were encountered: