Thanks for the explanation. In https://github.com/sagemath/sage/pull/40609,
I've tried to fix the small bugs in the docs that you pointed out. However,
> If I use the next button (say the Fedora part) the $ character is also
copied and the copied text gives an error in the terminal because of the $;
it is not a big deal but I guess it can be solved easily.
> In the same way, in the button of the block starting with "uv venv", only
three lines are copied (first, second and last). Again as above, it is not
a ...
seem to be actually bugs in sphinx (or I cannot figure out why the copy
button works in such a strange way there).
For the build issue, it's actually coming from
Traceback (most recent call last):
File "/usr/local/sagemeson/src/build-docs.py", line 8, in <module>
from sage_docbuild.__main__ import main
File "/usr/local/sagemeson/src/sage_docbuild/__main__.py", line 81, in
<module>
import sphinx.ext.intersphinx
File
"/home/artal/.local/lib/python3.13/site-packages/sphinx/ext/intersphinx.py",
line 37, in <module>
from sphinx.builders.html import INVENTORY_FILENAME
File
"/home/artal/.local/lib/python3.13/site-packages/sphinx/builders/html/__init__.py",
line 45, in <module>
from sphinx.writers.html import HTMLTranslator, HTMLWriter
File
"/home/artal/.local/lib/python3.13/site-packages/sphinx/writers/html.py",
line 21, in <module>
from sphinx.util.images import get_image_size
File
"/home/artal/.local/lib/python3.13/site-packages/sphinx/util/images.py",
line 4, in <module>
import imghdr
ModuleNotFoundError: No module named 'imghdr'
That is a result of a too-old sphinx, which is not compatible with python
3.13. After you update sphinx, the build should work.
Finally, I should note that
with https://github.com/sagemath/sage/pull/39030 sage-the-distro will also
use the meson build of sagelib.
On Saturday, August 16, 2025 at 11:25:00 PM UTC+8 enriqu...@gmail.com wrote:
> Thanks! My first remark is that it would be nice to have this in the
> documentation. The second point is that a classic build takes a while
> building sagelib. Is there a way to avoid this building and then perform a
> meson build of sagelib?
> Following your instructions in a classical build I did a meson build of
> sagelib (though I forgot the install part). I uninstalled sirocco and
> sagemath_sirocco, and fundamental groups did not work. Applying ./configure
> --enable-sirocco and make sirocco, the computations worked!
> Thanks, Enrique.
>
> El viernes, 15 de agosto de 2025 a las 20:07:05 UTC+2, dim...@gmail.com
> escribió:
>
> If you already done a classic build, then you don't need uv to do a meson
> build of sagelib.
> Just start
>
> ./sage --buildsh
>
> followed by meson commands as specified in the manual. Say, to have the
> meson builddir cp3, do
>
> meson setup cp3
>
> and then follow the meson commands in the manual
> (meson compile, etc)
>
> At the end your ./sage will be switched to using the meson-built sagelib,
> which you can test and use as usual.
>
>
>
> On August 15, 2025 9:49:22 AM EDT, "enriqu...@gmail.com" <
> enriqu...@gmail.com> wrote:
>
> In order to check https://github.com/sagemath/sage/pull/40555 I am trying
> to build sage with meson. I try to follow the instructions for 10.7 but I
> find some issues. I would appreciate some help that eventually may lead to
> improve the documentation.
> Before starting, if one copies the instructions in html, it is OK when in
> the rst the instruction
> is written in the file but $ is typed when it is an instruction
> following .. literalinclude
>
> I use the instructions for "Using system package manager". There is a
> warning after " uv pip install":
> warning: Failed to hardlink files; falling back to full copy. This may
> lead to degraded performance.
> If the cache and target directories are on different filesystems,
> hardlinking may not be supported.
> If this is intentional, set `export UV_LINK_MODE=copy` or use
> `--link-mode=copy` to suppress this warning.
> I do not know if this important. By the way should "--editable" should be
> added here of somewhere.
> For "uv sync --frozen --inexact --no-build-isolation" I get the error in
> the attached file.
>
> Thanks for reading. Enrique.
>
>
--
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 visit
https://groups.google.com/d/msgid/sage-devel/14cbc492-41a4-4b0a-beed-149c66c6d7cfn%40googlegroups.com.
