On 23 April 2024 19:48:18 BST, Marc Culler <marc.cul...@gmail.com> wrote:
>I discovered, by installing the Sage_macOS app on a pristine macOS system,
>that somehow, somewhere, in Sage's startup sequence there is a call to
>gcc. This is true whether Sage is being started from a command line or a
>notebook.
>
>On such a macOS system /usr/bin/gcc exists, but calling it causes a dialog
>to be posted which asks whether to download and install the Xcode "command
>line tools".
>
>There is no need for a user to install, or be prompted to install, a C
>compiler in order to run Sage. If we want to verify whether a C compiler
>is installed on the host system then we should check the return value of
>xcode-select
>-p rather than calling /usr/bin/gcc.
>
>I am unable to find where this call occurs. Do any of the Sage developers
>know which component of Sage could be calling /usr/bin/gcc on start up?
It's not quite correct to say that a C, or other, compiler is not required to
run Sage. Sage allows you to define, build, load, and run Cython extensions
without leaving Sage, thus, it needs to call a compiler after cythonisation
step.
It's another question why it's called on startup.
Might be macOS - only ?
Dima
>
>- Marc
>
--
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 on the web visit
https://groups.google.com/d/msgid/sage-devel/196ECB9F-6E79-4FEB-A928-9C20BCF7F673%40gmail.com.
