Yup, rerunning "mamba env update -n sage-build -f src/environment.yml"
installed eclib and now "./configure ..." produces one less error:
configure: error:
Given --with-system-primesieve=force, but no system package could be
used.
That's an error. Please install the indicated package to continue.
(To override this error, use ./configure --without-system-primesieve)
Given --with-system-primecount=force, but no system package could be
used.
That's an error. Please install the indicated package to continue.
(To override this error, use ./configure --without-system-primecount)
The documentation section about this is marked "experimental", and I think
this shows it's indeed not ready for prime time yet.
It sounds like https://trac.sagemath.org/ticket/33345 would also solve the
problem of depending on prone-to-change system libraries. Is that perhaps
the route to go for development nowadays? Then there's no conda/mamba to
worry about at all.
On Tuesday, 26 July 2022 at 06:12:52 UTC-7 Samuel Lelievre wrote:
> 2022-07-26 07:13:30 UTC, Dima Pasechnik:
>
> this says that conda is behind Sage in regard of versions of eclib
> and primesieve/count
>
> - eclib upgrade in Conda now done:
> https://github.com/conda-forge/eclib-feedstock/pull/36
> - primesieve and primecount seem up to date
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/7e754a78-42ff-4f88-bea4-31e851bfcbebn%40googlegroups.com.
