Okay, thanks. That helped a lot and made it so I could fix my compile-time issues.
That said, there is absolutely *no* way anybody except a sage build system expert could have found and known to do that. Also, I had no idea I should even look at meson/ninja logs for cython errors (much less where they would be located) either. We need proper displaying of error messages when builds fail. The generic slop I posted is completely unhelpful (thankfully, I knew it was a Cython compile issue because of what I was changing, but imagine if I didn't; e.g., a bad branch merge). There is a balance to be had, but we need more general verbosity in starting Sage when its running (potentially time consuming) build steps. Unfortunately I don't even have enough time to do the code I really need to do (even more so for should), nor do I have the expertise to help with the build system stuff. On Thursday, February 5, 2026 at 1:20:54 AM UTC+9 [email protected] wrote: On February 4, 2026 8:57:21 AM CST, "'[email protected]' via sage-devel" < [email protected]> wrote: On Wednesday, February 4, 2026 at 3:09:10 PM UTC+1 [email protected] wrote: 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. That's good to hear at least. Best, 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/70e71600-824d-4a84-a237-01b8fe4880ban%40googlegroups.com.
