That's probably due to a recent clang. Should be fixed by 
https://github.com/sagemath/sage/pull/39526 in the develop branch.

On Thursday, May 1, 2025 at 11:22:41 PM UTC+8 dim...@gmail.com wrote:

> It's hard to tell, but does your environment use Apple's toolchain, or 
> Conda toolchain.
> Could it be that you forgot to activate the Conda environment?
>
> Anyhow, I think 10.6 release is somewhat broken.
> Try the latest beta instead.
>
> Duma
>
> On 1 May 2025 09:06:00 GMT-05:00, Gareth Ma <grh...@gmail.com> wrote:
> >Hi all, this is yet another build problem with Sage.
> >
> >Background: I was helping David with building Sage 10.6 on his M2 Macbook
> >yesterday using the Meson build method. In particular, I don't have the 
> error
> >logs right now, but I believe David can reply and attach them later 
> (CC'ed).
> >
> >1. We started with a completely fresh source tarball download (10.6 
> stable).
> >
> >2. Then we installed Miniforge following following
> >https://doc.sagemath.org/html/en/installation/conda.html.
> >
> >3. Next, we followed 
> https://doc.sagemath.org/html/en/installation/meson.html
> >Creating the sage-dev Conda environment worked successfully.
> >
> >4. We then ran the `pip install --no-build-isolation --editable .`, but it
> >failed on the file src/sage/graphs/base/boost_interface.cpp
> >
> >More specifically, it errored on Line 119 (index[boost:source(...)]), 
> IIRC with
> >this error
> >
> >> error: non-constant-expression cannot be narrowed from type ... (aka 
> unsigned
> >long) to ... (aka int) in initializer list [-Wc++11-narrowing]
> >
> >Is this a known issue? What can cause this? In particular, it compiles on 
> my linux
> >
>

-- 
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/36544008-7d74-4612-bbca-36302fcbcbe9n%40googlegroups.com.

Reply via email to