On Sat, May 11, 2019 at 8:07 AM Dima Pasechnik wrote:
> On Sat, May 11, 2019 at 4:05 PM Dima Pasechnik wrote:
> > On Sat, May 11, 2019 at 3:55 PM Josh Haberman
> wrote:
> > > I tried installing gcc (which includes gfortran) from Homebrew, and
> then I set "export SAGE_INSTALL_GCC=no" but it tri
On Sat, May 11, 2019 at 4:05 PM Dima Pasechnik wrote:
>
> On Sat, May 11, 2019 at 3:55 PM Josh Haberman wrote:
> >
> > On Saturday, May 11, 2019 at 9:21:19 AM UTC-5, Dima Pasechnik wrote:
> >>
> >> On Sat, 11 May 2019 15:12 Josh Haberman, wrote:
> >>>
> >>> I just got the same error. I can attem
On Sat, May 11, 2019 at 3:55 PM Josh Haberman wrote:
>
> On Saturday, May 11, 2019 at 9:21:19 AM UTC-5, Dima Pasechnik wrote:
>>
>> On Sat, 11 May 2019 15:12 Josh Haberman, wrote:
>>>
>>> I just got the same error. I can attempt the workaround also, but is there
>>> a more permanent fix that wou
On Saturday, May 11, 2019 at 9:21:19 AM UTC-5, Dima Pasechnik wrote:
>
> On Sat, 11 May 2019 15:12 Josh Haberman, >
> wrote:
>
>> I just got the same error. I can attempt the workaround also, but is
>> there a more permanent fix that would avoid the need for the workaround?
>> Why is gfortran lo
On Sat, 11 May 2019 15:12 Josh Haberman, wrote:
> I just got the same error. I can attempt the workaround also, but is there
> a more permanent fix that would avoid the need for the workaround? Why is
> gfortran looking for this specific directory?
>
every sane Unix system, except MacOS 10.14, h
I just got the same error. I can attempt the workaround also, but is there
a more permanent fix that would avoid the need for the workaround? Why is
gfortran looking for this specific directory?
On Saturday, March 2, 2019 at 7:09:45 AM UTC-6, Jeremy Martin wrote:
>
> I just had to reinstall Sage
I just had to reinstall Sage (now running Mojave). I got the same error as
I had reported earlier, even though the command line tools were installed.
I followed Michael's suggestions and the build proceeded fine. Thank you!
-Jeremy
On Wednesday, October 10, 2018 at 9:47:45 PM UTC-5, Michael F
I get the same error with MAcOS Mojave and Xcode 10.0. The release notes
for Xcode 10 state that /usr/include is being relocated to
/Library/Developer//CommandLineTools/SDKs/MacOSX.sdk/usr/include/.
See the Xcode 10 release notes:
https://developer.apple.com/documentation/xcode_release_notes/
