Revision history [back]

When I tried to build Sage 9.2 on MacOS 10.11 using the (old, old) Xcode tools, numpy built, but building sagelib failed with errors pointing to problems with numpy.

I've succeeded in building 9.2 from the source tarball on OS X 10.11 using a 'minimal' Homebrew installation including gcc, mpfr, mpfi, gsl, libmpc, boost, gmp, and openblas. Homebrew no longer supports Apple systems running OS older than 10.12, but this worked well enough for me to build Sage.

Am I correct in concluding that the only way to duplicate this on a second (bootable) disk or on another computer running the same system is to duplicate this Homebrew setup and then build Sage from source again? The build time using an 8-core MacPro ca. 2008 only took about 90 minutes, but my other system only has a dual-core CPU.

I've read around a little and it seems that including scripts to relocate Sage are no longer viable with Python3. I also realize that I can just wait a few more days and pre-built binaries will be available. Here, I am just trying to understand the build process a little better. I've read about SAGE_ROOT and SAGE_LOCAL environment variables, but have not been able to figure out how to use them to relocate; I'm guessing this strategy is not possible.

The central question, then, is whether I need to install Homebrew everywhere I want to build Sage 9.2.

When I tried to build Sage 9.2 on MacOS 10.11 using the (old, old) Xcode tools, numpy built, but building sagelib failed with errors pointing to problems with numpy.

I've succeeded in building 9.2 from the source tarball on OS X 10.11 using a 'minimal' Homebrew installation including gcc, mpfr, mpfi, gsl, libmpc, boost, gmp, and openblas. Homebrew no longer supports Apple systems running OS older than 10.12, but this worked well enough for me to build Sage.

Am I correct in concluding that the only way to duplicate this on a second (bootable) disk or on another computer running the same system is to duplicate this Homebrew setup and then build Sage from source again? The build time using an 8-core MacPro ca. 2008 only took about 90 minutes, but my other system only has a dual-core CPU.

I've read around a little and it seems that including scripts to relocate Sage are no longer viable with Python3. I also realize that I can just wait a few more days and pre-built binaries will be available. Here, I am just trying to understand the build process a little better. I've read about SAGE_ROOT and SAGE_LOCAL environment variables, but have not been able to figure out how to use them to relocate; I'm guessing this strategy is not possible.

The central question, then, is whether I need to install Homebrew everywhere I want to build Sage 9.2.

When I tried to build Sage 9.2 on MacOS 10.11 using the (old, old) Xcode tools, numpy built, but building sagelib failed with errors pointing to problems with numpy.

I've succeeded in building 9.2 from the source tarball on OS X 10.11 using a 'minimal' Homebrew installation including gcc, mpfr, mpfi, gsl, libmpc, boost, gmp, and openblas. Homebrew no longer supports Apple systems running OS older than 10.12, but this worked well enough for me to build Sage.

Am I correct in concluding that the only way to duplicate this on a second (bootable) disk or on another computer running the same system is to duplicate this Homebrew setup and then build Sage from source again? The build time using an 8-core MacPro ca. 2008 only took about 90 minutes, but my other system only has a dual-core CPU.

I've read around a little and it seems that including scripts to relocate Sage are no longer viable with Python3. I also realize that I can just wait a few more days and pre-built binaries will be available. Here, I am just trying to understand the build process a little better. I've read about SAGE_ROOT and SAGE_LOCAL environment variables, but have not been able to figure out how to use them to relocate; I'm guessing this strategy is not possible.

The central question, then, is whether I need to install Homebrew everywhere I want to build Sage 9.2.

[Afterthought: I thought I could include the path to my Homebrew installation when building on the other local disks.]disks, but even with this at the top of the path, it doesn't work for me - the Sage build script stills sees the old /usr/bin/gcc.]

When I tried to build Sage 9.2 on MacOS 10.11 using the (old, old) Xcode tools, numpy built, but building sagelib failed with errors pointing to problems with numpy.

I've succeeded in building 9.2 from the source tarball on OS X 10.11 using a 'minimal' Homebrew installation including gcc, mpfr, mpfi, gsl, libmpc, boost, gmp, and openblas. Homebrew no longer supports Apple systems running OS older than 10.12, but this worked well enough for me to build Sage.

Am I correct in concluding that the only way to duplicate this on a second (bootable) disk or on another computer running the same system is to duplicate this Homebrew setup and then build Sage from source again? The build time using an 8-core MacPro ca. 2008 only took about 90 minutes, but my other system only has a dual-core CPU.

I've read around a little and it seems that including scripts to relocate Sage are no longer viable with Python3. I also realize that I can just wait a few more days and pre-built binaries will be available. Here, I am just trying to understand the build process a little better. I've read about SAGE_ROOT and SAGE_LOCAL environment variables, but have not been able to figure out how to use them to relocate; I'm guessing this strategy is not possible.

The central question, then, is whether I need to install Homebrew everywhere I want to build Sage 9.2.

[Afterthought: [Afterword: I thought I could include the path to my Homebrew installation when building on the other local disks, but even with this at the top of the path, it doesn't work for me - the Sage build script stills still sees the old /usr/bin/gcc.]

When I tried to build Sage 9.2 on MacOS 10.11 using the (old, old) Xcode tools, numpy built, but building sagelib failed with errors pointing to problems with numpy.

I've succeeded in building 9.2 from the source tarball on OS X 10.11 using a 'minimal' Homebrew installation including gcc, mpfr, mpfi, gsl, libmpc, boost, gmp, and openblas. Homebrew no longer supports Apple systems running OS older than 10.12, but this worked well enough for me to build Sage.

Am I correct in concluding that the only way to duplicate this on a second (bootable) disk or on another computer running the same system is to duplicate this Homebrew setup and then build Sage from source again? The build time using an 8-core MacPro ca. 2008 only took about 90 minutes, but my other system only has a dual-core CPU.

I've read around a little and it seems that including scripts to relocate Sage are no longer viable with Python3. I also realize that I can just wait a few more days and pre-built binaries will be available. Here, I am just trying to understand the build process a little better. I've read about SAGE_ROOT and SAGE_LOCAL environment variables, but have not been able to figure out how to use them to relocate; I'm guessing this strategy is not possible.

The central question, then, is whether I need to install Homebrew everywhere I want to build Sage 9.2.

When I tried to build Sage 9.2 on MacOS 10.11 using the (old, old) Xcode tools, numpy built, but building sagelib failed with errors pointing to problems with numpy.

I've succeeded in building 9.2 from the source tarball on OS X 10.11 using a 'minimal' Homebrew installation including gcc, mpfr, mpfi, gsl, libmpc, boost, gmp, and openblas. Homebrew no longer supports Apple systems running OS older than 10.12, but this worked well enough for me to build Sage.

Am I correct in concluding that the only way to duplicate this on a second (bootable) disk or on another computer running the same system is to duplicate this Homebrew setup and then build Sage from source again? The build time using an 8-core MacPro ca. 2008 only took about 90 minutes, but my other system only has a dual-core CPU.

I've read around a little and it seems that including scripts to relocate Sage are no longer viable with Python3. I also realize that I can just wait a few more days and pre-built binaries will be available. Here, I am just trying to understand the build process a little better. I've read about SAGE_ROOT and SAGE_LOCAL environment variables, but have not been able to figure out how to use them to relocate; I'm guessing this strategy is not possible.

The central question, then, is whether I need to install Homebrew everywhere I want to build Sage 9.2.9.2. I think so, because that is how the Sage build system finds those tools.

When I tried to build Sage 9.2 on MacOS 10.11 using the (old, old) Xcode tools, numpy built, but building sagelib failed with errors pointing to problems with numpy.

I've succeeded in building 9.2 from the source tarball on OS X 10.11 using a 'minimal' Homebrew installation including gcc, mpfr, mpfi, gsl, libmpc, boost, gmp, and openblas. Homebrew no longer supports Apple systems running OS older than 10.12, but this worked well enough for me to build Sage.

Am I correct in concluding that the only way to duplicate this on a second (bootable) disk or on another computer running the same system is to duplicate this Homebrew setup and then build Sage from source again? The build time using an 8-core MacPro ca. 2008 only took about 90 minutes, but my other system only has a dual-core CPU.

I've read around a little and it seems that including scripts to relocate Sage are no longer viable with Python3. I also realize that I can just wait a few more days and pre-built binaries will be available. Here, I am just trying to understand the build process a little better. I've read about SAGE_ROOT and SAGE_LOCAL environment variables, but have not been able to figure out how to use them to relocate; I'm guessing this strategy is not possible.

The central question, then, is whether I need to install Homebrew everywhere I want to build Sage 9.2. I think so, because that is how the Sage build system finds those tools.

When I tried to build Sage 9.2 on MacOS 10.11 using the (old, old) Xcode tools, numpy built, but building sagelib failed with errors pointing to problems with numpy.

I've succeeded in building 9.2 from the source tarball on OS X 10.11 using a 'minimal' Homebrew installation including gcc, mpfr, mpfi, gsl, libmpc, boost, gmp, and openblas. Homebrew no longer supports Apple systems running OS older than 10.12, but this worked well enough for me to build Sage.

Am I correct in concluding that the only way to duplicate this on a second (bootable) disk or on another computer running the same system is to duplicate this Homebrew setup and then build Sage from source again? The build time using an 8-core MacPro ca. 2008 only took about 90 minutes, but my other system only has a dual-core CPU.

I've read around a little and it seems that including scripts to relocate Sage are no longer viable with Python3. I also realize that I can just wait a few more days and pre-built binaries will be available. Here, I am just trying to understand the build process a little better. I've read about SAGE_ROOT and SAGE_LOCAL environment variables, but have not been able to figure out how to use them to relocate; I'm guessing this strategy is not possible.

The central question, then, is whether I need to install Homebrew everywhere I want to build Sage 9.2. I think so, because that is how the Sage build system finds those tools.

Note on packages in Homebrew: no need to add gsl, or openblas; Sage builds these anyway.