On Tuesday, November 26, 2024 at 8:45:37 PM UTC+9 Dima Pasechnik wrote: no, I have not yet opened a PR to fix it.
The PR should be a blocker. It was added in the PR which upgraded gcc - as it failed to build ecm on a macOS system (sic!) On macOS, I think it is the usual scenario that the system gcc(clang) is used to build sage. We should just get rid of the gcc package, it is merely a source of bugs and a general development timesink. I am aware that this issue is controversial. But I am no expert in that. If, on every platform we support, the system gcc is a prerequisite and enough to build sage, and to compile cython code in sage sessions, then I see no reason for us to carry the gcc package. I wonder what are the main arguments against it though. -- You received this message because you are subscribed to the Google Groups "sage-release" 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-release/555ee36c-24e9-4d6c-b471-91b0f101d236n%40googlegroups.com.
