Hi Dima,
> Why would you want to remove Brew---unless you enjoy building gfortran
> and gmp from source ? :-)
I definitely do not want to remove brew but the fact is that I could not
compile sage while it it was present because of an unidentified conflict.
Note that I did not say that I
Why would you want to remove Brew---unless you enjoy building gfortran
and gmp from source ? :-)
I'd rather suggest we make an effort to create and use as many Brew
packages (perhaps from our own) Brew (formulae) repo.
I've just transferred the repo with few Brew formulae I wrote to sagemath org:
Thanks Justin, François and Dima, your comments were helpful. I used to
quaranteen brew from my sage builds but I stopped doing this because others
managed to compile sage along side homebrew, and even recommended which
packages to install, and I was able to do this before macos 10.15. When I
Thanks Justin, François and Dima, your comments were helpful. I used to
quaranteen brew from my sage builds but I stopped doing this because others
managed to compile sage along side homebrew, and even recommended which
packages to install, and I was able to do this before macos 10.15. When I
On Sun, Jan 26, 2020 at 12:03 AM 'Justin C. Walker' via sage-devel
wrote:
>
>
>
> > On Jan 25, 2020, at 15:21 , Andrew wrote:
> >
> > On sage-release Justin C Walker has reported successfully compiled sage
> > 9.1.beta1 on a 2019 MBP, 8-core Core i9 running 10.5.2.
> >
> > I am running 10.5.2
> On Jan 25, 2020, at 15:21 , Andrew wrote:
>
> On sage-release Justin C Walker has reported successfully compiled sage
> 9.1.beta1 on a 2019 MBP, 8-core Core i9 running 10.5.2.
>
> I am running 10.5.2 on 2016 MBP, 4-core Core i7 and, as previously reported,
> I whenever I try to compile
It looks to me like there could be a bad interaction between compiler headers
(probably installed by brew)
in /usr/local and system headers.
If it is not then I would think there could be a bug for upstream givaro.
François
> On 26/01/2020, at 12:21 PM, Andrew wrote:
>
> On sage-release
