No, you do NOT need "proper" gcc to build Sage on OSX, you need OSX's
clang/clang++
OSX in its infinite wisdom aliases clang to gcc.

One cannot build Sage on OSX with "real" gcc.
That is, your "gcc" should be /usr/bin/gcc, which is actually clang.



On Tue, Oct 8, 2019 at 5:56 PM Zachary Scherr <[email protected]> wrote:

> Hi Dima,
>
>    I have, but I noticed something interesting which is that gcc and g++
> are no longer symlinked in my /usr/local/bin.  I have gcc-9 and g++-9 in
> there, but when I try "which gcc" and "which g++" I get /usr/bin/gcc and
> /usr/bin/g++ which are the versions installed by command line tools.  This
> is making me even more confused because sage didn't even attempt to build
> with the version of gcc installed by homebrew.
>
>    I'm currently retesting with gcc and g++ symlinked to the new version.
> I'll let you know if I have any success.
>
> Thanks,
> Zach
>
> On Tuesday, October 8, 2019 at 4:25:23 PM UTC-4, Dima Pasechnik wrote:
>>
>> did you try updating homebrew?
>>
>> I think that what ultimately helped Ben to get a working gfortran, and
>> correctly build whatever scipy's dependency is causing the problem.
>>
>>
>> On Tue, Oct 8, 2019 at 3:17 PM Zachary Scherr <[email protected]> wrote:
>>
>>> In an attempt to add openssl to sage I ran: sage -i openssl && sage -f
>>> python2 (which I've done successfully in every previous version of Sage
>>> 8.x).
>>>
>>> The sage -f python2 failed while trying to build scipy-1.2.0.  This may
>>> be related to Ben's post
>>> https://groups.google.com/forum/#!topic/sage-devel/40E66JVHhW8 since it
>>> also failed with the message
>>>
>>> ld: library not found for -lSystem
>>>
>>> I too have gcc installed through homebrew, but I also tried removing it
>>> and installing gfortran separately and ended up with the same error.  I've
>>> attached the log file, anyone know what's going on?
>>>
>>>
>>>
>>> --
>>> 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 on the web visit
>>> https://groups.google.com/d/msgid/sage-devel/5a356d10-a069-487a-a75c-ace33ba11f07%40googlegroups.com
>>> <https://groups.google.com/d/msgid/sage-devel/5a356d10-a069-487a-a75c-ace33ba11f07%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> 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 on the web visit
> https://groups.google.com/d/msgid/sage-devel/cd8fa4be-df55-42a4-aeb3-d747fc42fbda%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-devel/cd8fa4be-df55-42a4-aeb3-d747fc42fbda%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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 on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq0u5xsmYe6cYCtxeoqjt0Vn5gfaD2jRsvmBhwuoPEJycA%40mail.gmail.com.

Reply via email to