Since I'm also on ArchLinux, I have the same issue. I found that I can fix things if I manually patch out `-I /usr/include` in the generated jinja.build file. It seems that this causes trouble because ArchLinux's NTL/config.h has #define NTL_THREADS which conda-forge's does not have.
So, the include paths I see in the ninja file always have this shape: -Isrc/sage/... and -I../../src/sage/... -Ipath-to-conda-env/lib/python3.12/site-packages/cypari2 -Ipath-to-conda-env/lib/python3.12/site-packages/cysignals -Ipath-to-conda-env/include/python3.12 -I/usr/include -Ipath-to-conda-env/include and then some more conda paths So why is /usr/include coming before the conda paths? I don't see this anywhere in my environment variables. It might actually be related to the cmake bits you posted earlier. If you ask cmake for cblas compiler switches it reports /usr/include. Is that somehow invoked in the setup? I don't really understands how the ninja build file is generated but if somebody can point me to the correct place, I am happy to provide a PR for this. julian On Thursday, January 29, 2026 at 10:22:25 AM UTC+1 vdelecroix wrote: > With Julian at sage days 130 we noticed other fishy things happening > > 1) (minor) cmake was not installed in the conda environment > > 2) (problematic but probably not critical) both system cmake and conda > cmake thinks that my blas and cblas are better from the system > > $ micromamba activate sage-dev > (sage-dev) $ cmake --find-package -DNAME=CBLAS -DCOMPILER_ID=GNU > -DLANGUAGE=CXX -DMODE=LINK > /usr/lib/libcblas.so.3.12.0 /usr/lib/libblas.so.3.12.0 > > On Thu, 29 Jan 2026 at 00:08, Dima Pasechnik <[email protected]> wrote: > > > > On Wed, Jan 28, 2026 at 4:54 PM Vincent Delecroix > > <[email protected]> wrote: > > > > > > Hello, > > > > > > In a clone of 10.9.beta4, I created a fresh conda environment > > > > > > $ micromamba env create --file environment-3.13-linux.yml --name > sage-dev > > > > > > activated it > > > > > > $ micromamba activate sage-dev > > > > > > and tried to build sage in it > > > > > > (sage-dev)$ pip install --no-build-isolation --editable . > > > > > > but it failed at Cython compilation (see attached file). > > > > > > Any idea on how to solve it? > > > > there is an NTL/flint error, did you notice? > > Apperently Conda's NTL is non-TLS? > > > > > /home/vincent/micromamba/envs/sage-dev/bin/../libexec/gcc/x86_64-conda-linux-gnu/14.3.0/ld: > > _ZN3NTL8zz_pInfoE: TLS reference in src/sage/ > > > libs/linbox/linbox_flint_interface.cpython-313-x86_64-linux-gnu.so.p/meson-generated_src_sage_libs_linbox_linbox_flint_interface.pyx.cpp.o > > mism > > atches non-TLS definition in > > /home/vincent/micromamba/envs/sage-dev/lib/libntl.so section .bss > > > /home/vincent/micromamba/envs/sage-dev/bin/../libexec/gcc/x86_64-conda-linux-gnu/14.3.0/ld: > > /home/vincent/micromamba/envs/sage-dev/lib/li > > bntl.so: error adding symbols: bad value > > collect2: error: ld returned 1 exit status > > > > > > > > Best > > > Vincent > > > > > > -- > > > 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/CAGEwAAkmeAnmGrzWMjT58-97Ow1kT-8wY_aqKqSV5DGrxkGKWg%40mail.gmail.com > . > -- 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/1c4bdcb6-1809-4bed-87b9-d1e5995d7ea4n%40googlegroups.com.
