Error building Sage using WSL

150 views
Skip to first unread message

Kyrie

unread,
Nov 12, 2024, 10:59:54 AM11/12/24
to sage-devel
Hi,

I'm trying to build SageMath on my machine -- 16 GB RAM, Windows 11 (build 22631.4317) -- using WSL. 

I'm following the instructions at https://github.com/sagemath/sage/#readme. When I get to step 14 and run "make", I get

"Error building Sage.
The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):
* package:         python3-3.12.4
  last build time: Nov 10 19:02
  log file:        /home/kyrie/sage/sage/logs/pkgs/python3-3.12.4.log"

The log file is attached.

When I run "sudo apt-get install python3 libpython3-dev python3-setuptools       python3-venv" again, I get
"python3 is already the newest version (3.12.3-0ubuntu2).
libpython3-dev is already the newest version (3.12.3-0ubuntu2).
python3-setuptools is already the newest version (68.1.2-2ubuntu1.1).
python3-venv is already the newest version (3.12.3-0ubuntu2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded."

I had Python on my machine before adding WSL for the purpose of Sage. So I also thought to look back at the environment variables PATH, PKG_CONFIG_PATH, LD_LIBRARY_PATH, CFLAGS, CPPFLAGS, CXXFLAGS, and LDFLAGS to verify that there are no items beginning with "/mnt/c" as in Step 8 of the ReadMe.

I'm deeply grateful for any suggestions for how else to troubleshoot / how to get Sage to build!

With gratitude,
Kyrie




python3-3.12.4.log

Dima Pasechnik

unread,
Nov 12, 2024, 2:39:03 PM11/12/24
to sage-...@googlegroups.com, slilv...@gmail.com
Hello,
the easiest in your case would be to use the Python you already have
installed in WSL.
In principle, the installation (./configure script) should be able to
detect it, and use it, instead of trying to build Python.
Please post config.log (in the main Sage directory, where you run make
etc) - then we can see what's up with it.
> --
> 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+...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/sage-devel/cfc55b00-6ba5-499b-a425-d989089f614en%40googlegroups.com.

Kyrie

unread,
Nov 15, 2024, 7:03:47 PM11/15/24
to sage-devel
Hi,

Thank you for the suggestion. I've attached the config.log.
config.log

Dima Pasechnik

unread,
Nov 18, 2024, 12:01:49 PM11/18/24
to sage-...@googlegroups.com, slilv...@gmail.com
Hi,

you are using a python from miniforge,
not the system python.

If you really want to using miniforge (i.e. conda), it needs a special treatment.

You cannot freely mix system packages and conda, you either activate a conda environment and do everything there.

Otherwise, make sure that conda doesn't interfere. (make sure there is nothing related to  it in PATH).

HTH,
Dima

Dima Pasechnik

unread,
Nov 18, 2024, 12:02:01 PM11/18/24
to Kairi Black, sage-...@googlegroups.com
Hi,
On Sun, Nov 17, 2024 at 10:36:24AM -0500, Kairi Black wrote:
>
> Thank you for the help/suggestions. I am still receiving a Python build
> error when running "make".

Your ./configure run ended with an error, and you didn't notice.
Namely, it complained that you don't have m4 installed (previously you
had one in conda, I suppose).
No wonder you then get strange errors trying to run make.

Please remove everything starting from /usr/local/ from your PATH
(from the PATH in for the WSL prompt you will build and run Sage)

Please run (in the WSL prompt)
the following, as specified in https://doc.sagemath.org/html/en/installation/source.html#sec-installation-from-sources

make distclean # to start from scratch

sudo apt-get install bc binutils bzip2 ca-certificates cliquer cmake curl \
ecl eclib-tools fflas-ffpack g++ gap gcc gengetopt gfan gfortran \
glpk-utils gmp-ecm lcalc libatomic-ops-dev libboost-dev \
libbraiding-dev libbrial-dev libbrial-groebner-dev libbz2-dev \
libcdd-dev libcdd-tools libcliquer-dev libcurl4-openssl-dev libec-dev \
libecm-dev libffi-dev libflint-dev libfplll-dev libfreetype-dev \
libgap-dev libgc-dev libgd-dev libgf2x-dev libgiac-dev libgivaro-dev \
libglpk-dev libgmp-dev libgsl-dev libhomfly-dev libiml-dev \
liblfunction-dev liblinbox-dev liblrcalc-dev liblzma-dev libm4ri-dev \
libm4rie-dev libmpc-dev libmpfi-dev libmpfr-dev libncurses5-dev \
libntl-dev libopenblas-dev libpari-dev libplanarity-dev libppl-dev \
libprimecount-dev libprimesieve-dev libpython3-dev libqhull-dev \
libreadline-dev librw-dev libsingular4-dev libsqlite3-dev libssl-dev \
libsuitesparse-dev libsymmetrica2-dev libz-dev libzmq3-dev m4 make \
maxima maxima-sage meson nauty ninja-build openssl palp pari-doc \
pari-elldata pari-galdata pari-galpol pari-gp2c pari-seadata patch \
patchelf perl pkg-config planarity ppl-dev python3 python3-setuptools \
python3-venv qhull-bin singular singular-doc sqlite3 sympow tachyon \
tar texinfo tox xcas xz-utils

(some of these are already installed, but not all). Then run


./configure
make

>
> I tried the following:
>
> 1. Remove any references to miniforge from my PATH variable. (get Python
> build error when run "make")
> 2. Uninstall miniforge using the instructions at
> https://github.com/conda-forge/miniforge. (get Python build error when run
> "make")
> 3. Uninstall and reinstall Python3.12 in WSL using
> https://gist.github.com/zhensongren/811dcf2471f663ed3148a272f1faa957, then
> running
>
> sudo apt-get install libpython3-dev python3-setuptools python3-venv
>
> as in https://doc.sagemath.org/html/en/reference/spkg/python3.html. (Then
> still get Python build error when run "make" and "configure")
>
> I've attached the python build log, and the config log.
>
> I'm grateful for your patience with me (a person new to Linux, who is using
> WSL for the first time in an effort to use Sage on my Windows machine).
>
> And appreciative of any additional recommendations or clarifications on
> what isn't working!
>
> -Kyrie
signature.asc
Reply all
Reply to author
Forward
0 new messages