On February 4, 2026 8:57:21 AM CST, "'[email protected]' via sage-devel" < [email protected]> wrote:
> You can try the verbose mode by setting the env variable > `MESONPY_EDITABLE_VERBOSE`, see > https://mesonbuild.com/meson-python/how-to-guides/editable-installs.html#verbose-mode > > Ad 1: it's the documentation build. This should be fixed by > https://github.com/sagemath/sage/pull/41156 and > https://github.com/sagemath/sage/pull/41162 but I currently don't have > much time to work on this myself. So help eg in the form of PRs against the > PR-branch is very welcome. > indeed, "export MESONPY_EDITABLE_VERBOSE=1" should make building more verbose Also, after https://github.com/sagemath/sage/pull/41418 (should be in the latest betas) ./configure --disable-doc will make rebuilding much quicker (the time was wasted otherwise in meson scanning documents in src/doc) Merged last week https://github.com/sagemath/sage/pull/41174 tells "sage -b" to run menson directly Regarding the build logs. Meson logs are in build/sage-distro/meson-logs/ and ninja logs are in build/sage-distro/.ninja_log > > On Wednesday, February 4, 2026 at 3:09:10 PM UTC+1 [email protected] > wrote: > >> It just does this: >> >> tscrim@travis-apricot:~$ sage >> Traceback (most recent call last): >> File >> "/home/tscrim/sage/local/var/lib/sage/venv-python3.12.5/lib/python3.12/site-packages/_sagemath_editable_loader.py", >> line 345, in _rebuild >> subprocess.run(self._build_cmd, cwd=self._build_path, env=env, >> stdout=subprocess.DEVNULL, check=True) >> File >> "/home/tscrim/sage/local/var/lib/sage/venv-python3.12.5/lib/python3.12/subprocess.py", >> line 571, in run >> raise CalledProcessError(retcode, process.args, >> subprocess.CalledProcessError: Command '['/usr/bin/ninja']' returned >> non-zero exit status 1. >> >> The above exception was the direct cause of the following exception: >> >> Traceback (most recent call last): >> File "/home/tscrim/sage/src/bin/sage-ipython", line 9, in <module> >> from sage.misc.banner import banner >> File >> "/home/tscrim/sage/local/var/lib/sage/venv-python3.12.5/lib/python3.12/site-packages/_sagemath_editable_loader.py", >> line 311, in find_spec >> tree = self._rebuild() >> ^^^^^^^^^^^^^^^ >> File >> "/home/tscrim/sage/local/var/lib/sage/venv-python3.12.5/lib/python3.12/site-packages/_sagemath_editable_loader.py", >> line 347, in _rebuild >> raise ImportError(f're-building the {self._name} meson-python >> editable wheel package failed') from exc >> ImportError: re-building the sagemath meson-python editable wheel package >> failed >> >> Thus I cannot debug Cython errors unless I run "sage -b", which takes >> forever because the meson setup takes multiple minutes every time. >> >> Two things we (specifically the people changing stuff in the build >> system) **really** need to do because this is unsustainable for Cython >> development in Sage: >> >> 1) Figure out what makes meson take so long to do its thing each time >> "sage -b" is run because this significantly slows many things down. >> 2a) Display the error message when cython builds fail so we can debug >> cython errors with the magic compiling. (I still *very* strongly believe we >> should give a message saying Cython code is recompiling verbosely on the >> files so it doesn't look like it is hanging. I also believe it is bad >> practice to make a non-jit-compiled language act like a jit-compiled >> language, but that is secondary.) >> > this is "export MESONPY_EDITABLE_VERBOSE=1" 2b) Revert "sage -b" to actually just rebuilding the parts of Sage that >> should be rebuilt/recompiled; meson is not part of this AFAIK. >> > after https://github.com/sagemath/sage/pull/41174 "sage -b" does ninja -C $SAGE_ROOT/build/sage-distro (you can also run this explictly) Tobias says it's not 100% fool-proof from meson point of view, but it's certainly fast and should very quickly rebuild what's needed. Dima >> Travis >> > -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq1M%2BbZF95z4oZTdyMSKbMmCuUerA0k0SOEOFaF7j%2B-qJg%40mail.gmail.com.
