cython broken in OSX packages

[Vincent Delecroix]

Hello,

At sage days 73 I did some Sage install from the binaries available on
internet. For some of them Cython is just broken (complaining that gcc
is not available). Are Sage users supposed to have gcc on their
computer? Is there a way to test the .dmg package automatically?

It is the very same problem as with the Ubuntu package that I reported in

https://groups.google.com/forum/#!topic/sage-devel/D9bnqyrmF40

Vincent

[kcrisman]

On Thursday, May 5, 2016 at 8:50:26 AM UTC-4, vdelecroix wrote:

Hello,

At sage days 73 I did some Sage install from the binaries available on
internet. For some of them Cython is just broken (complaining that gcc
is not available). Are Sage users supposed to have gcc on their
computer? 

I don't think that is necessary but maybe we should be louder about it.  Nowadays you can get command line tools just by opening a terminal and typing a command that needs them, e.g.

$ git

<message about installing command line tools>

but we should indeed expect Cython to be broken (and %fortran and other things of that nature) if they don't have the command line tools, which many users won't by default.