your config.log says you have leftovers from the previous attempt to install,
which was unsuccessful due to conda issues.
Please clean up by running
make distclean
and then start again with
./bootstrap
./configure
make
On 26 January 2025 17:17:11 GMT-06:00, Caleb Van't Land
wrote:
>I wa
by the way, it's not clear what version you downloaded. The URL you posted
lists a lot of different ones.
we recommend getting sources from GitHub using git.
On 26 January 2025 12:07:21 GMT-06:00, Anna wrote:
>
>
>Hi,
>
>I am not very experienced with installing software and dependencies so
On Sun, Jan 26, 2025 at 01:33:24PM -0600, Marc Culler wrote:
> OK. But clearly it is a bug that the CoxeterGroup package raises:
> RuntimeError: coxeter3 must be installed
> when coxeter3 *is* installed but sagemath_coxeter3 is not installed.
naming conventions...
Python package coxeter3 is ins
On 2025-01-26 11:03:42, Marc Culler wrote:
> Yes, I have a log file for coxeter3 which built fine.
>
> The problem turned out to be that I had to use BOTH ---enable-coxeter3 AND
> -enable-sagemath_coxeter3. With the latter option, the .so file gets build
> and installed as expected.
>
> Why?
On Sun, Jan 26, 2025 at 11:03:42AM -0800, Marc Culler wrote:
> Yes, I have a log file for coxeter3 which built fine.
>
> The problem turned out to be that I had to use BOTH ---enable-coxeter3 AND
> -enable-sagemath_coxeter3. With the latter option, the .so file gets build
> and installed as exp
OK. But clearly it is a bug that the CoxeterGroup package raises:
RuntimeError: coxeter3 must be installed
when coxeter3 *is* installed but sagemath_coxeter3 is not installed.
- Marc
On Sun, Jan 26, 2025 at 1:28 PM wrote:
> On Sun, Jan 26, 2025 at 11:03:42AM -0800, Marc Culler wrote:
> > Yes
Just to confirm, after I installed sagemath_coxeter3 the computation which
was reported on sage-support as failing, and which produced the traceback
saying that coxeter3 needed to be installed, now works fine:
┌─┐
│ SageMath version 10.6.beta4, Release
Please install gfortran system-wide; something like (I assume you are on a
Debian/Ubuntu-like distro, as I gather from the config.log)
sudo apt-get install gfortran
and try again.
In general, please run ./configure, and pay attention to the list of
system-wide packages it asks/recommends to be i
Yes, I have a log file for coxeter3 which built fine.
The problem turned out to be that I had to use BOTH ---enable-coxeter3 AND
-enable-sagemath_coxeter3. With the latter option, the .so file gets build
and installed as expected.
Why? What is this about? And why does the traceback tell our
On Sun, Jan 26, 2025 at 11:51 AM Marc Culler wrote:
>
> In the venv of my recently built SageMath-10.6beta4 I find:
> % ls lib/python3.12/site-packages/sage/libs/coxeter3
> __init__.py coxeter.pxd decl.pxd __pycache__ coxeter.pyx
> all__sagemath_coxeter3.py coxeter_group.py
>
> In other subdirec
The coxeter3 package is not the only one. The optional packages meataxe and
sirocco also have .pyx files with no associated .so file. Those three are
the only optional packages which appear in
venv/lib/python3.12/site-packages/sage/libs
even though many other optional packages are enabled by my
In the venv of my recently built SageMath-10.6beta4 I find:
% ls lib/python3.12/site-packages/sage/libs/coxeter3
__init__.py coxeter.pxd decl.pxd __pycache__ coxeter.pyx
all__sagemath_coxeter3.py coxeter_group.py
In other subdirectories of sage/libs, such as flint, one finds that every
.pyx fi
12 matches
Mail list logo
