I think there is no need to make Homebrew build gcc from source. (and
again, you only need gfortran, so make sure there is no "real" gcc in your
PATH)
It's much more likely just the problem of using a binary built of Sage.
On Tue, Oct 8, 2019 at 10:47 PM Zachary Scherr wrote:
> Will do. It also
Will do. It also occurs to me that maybe I should force Homebrew to build
GCC from source first and see if that works. I'll experiment some more and
let you know how it goes. Thank you for the help.
On Tuesday, October 8, 2019 at 11:44:53 PM UTC-4, Dima Pasechnik wrote:
>
> Note that Ben was
Note that Ben was building Sage from source, whereas you're trying to
modify a binary Sage installation, something that is more error-prone.
Would you mind trying to build from source instead?
On Tue, Oct 8, 2019 at 10:22 PM Zachary Scherr wrote:
> That makes sense. I also tried installing
That makes sense. I also tried installing gcc@8 and symlinking gfortran to
make it point to the older version, but everything I've tried fails at the
same point.
On Tuesday, October 8, 2019 at 7:14:49 PM UTC-4, Dima Pasechnik wrote:
>
> No, you do NOT need "proper" gcc to build Sage on OSX, you
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
On OS X, Sage by default should use the system's "gcc" (which is actually
clang), so it's okay to not have a symlink connecting gcc-9 to gcc in
/usr/local/bin. What you really need is /usr/local/bin/gfortan, and
homebrew should provide that.
John
On Tuesday, October 8, 2019 at 3:56:24 PM
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
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 wrote:
> In an attempt to add openssl to sage I ran: sage -i openssl && sage
I've just posted NTL 11.4.1, which fixes a bug introduced in NTL 11.4.0.
Details here: https://shoup.net/ntl/
--
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
