On Sunday, October 19, 2025 at 1:41:41 AM UTC+9 Michael Orlitzky wrote: On 2025-10-18 08:43:13, Travis Scrimshaw wrote: > Okay, perhaps I should be more precise here (it's also been awhile since I > used one, so my memory might be wrong). On any single command, it doesn't > say anything (it would be difficult for it to say what it was doing), but > when run from a makefile, I thought it did output what command was being > run? (Okay, technically that isn't a C compiler either...but the act of > compiling a C program.)
"make" will print the commands it's running, but I was not seriously trying to nitpick, your point was clear. When you run GCC, you expect it to be compiling a C program; when you run Sage, you expect to see a Sage banner. My earlier message was not defending the behavior, only pointing out that spin doesn't solve it. If you are willing to forego the editable install, then meson alone works great. If not, the problem lies one level below spin. I know, but I think it is important to make sure the point can't be defeated by technicalities. :) -- 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/a0b4e3fc-68a0-4ec7-935a-e809dad19256n%40googlegroups.com.
