ASKSAGE: Sage Q&A Forum - Individual question feedhttp://ask.sagemath.org/questions/Q&A Forum for SageenCopyright Sage, 2010. Some rights reserved under creative commons license.Thu, 01 Aug 2019 10:55:20 -0500Building Sage on legacy macos system 10.5.8http://ask.sagemath.org/question/47324/building-sage-on-legacy-macos-system-1058/This isn't a question, yet, depending on replies. It's more of a good-news story (for me, anyway). I'm a hobbyist with legacy mac systems and pretty much a newbie with Sage commands per se, and wanted to use the experience to get a better handle on the structure and behavior of the build system. I just hope this adds to the mac build knowledge base for Sage.
I've just successfully built sage-6.10 (downloaded from the git repository) on a mac book 4,1 system with a Core2Duo processor that does not upgrade MacOS beyond Snow Leopard. The total build time was about 8 hours starting with Xcode 3.2. I had difficulties getting started because all my more modern tools are in my macports installation, and I haven't installed upgrades anywhere else --- or so I thought at first. I hit upon including the path to a previous Sage installation which I did some years ago with a binary download of sage-5.13, adding the path to Sage's local/bin. And it worked!
I had one glitch with the installation of flint-2.5.2, when its makefile died with a request to cp -a which happened after:
mkdir -p "./sage-6.10/local/lib"
mkdir -p "./sage-6.10/local/include/flint"
In my os x shell, there is no cp -a and I substituted cp -pPR by using the debug shell for the build system. Everything else went off without a hitch. What a marvelously robust build system this is, given a finicky set of standard mac build tools! Perhaps I should not find it remarkable that I can still do a build like this with a ten-or-more-year-old computer running a 12-year-old OS.
My question is this: I am having trouble locating solid information about which versions of Sage I should try to build for some particular version of the OS. It it just going to be a matter of dedicated experimentation? If so, my experience here tells me I am ready for that.Wed, 31 Jul 2019 04:57:36 -0500http://ask.sagemath.org/question/47324/building-sage-on-legacy-macos-system-1058/Comment by dyne2meter for <p>This isn't a question, yet, depending on replies. It's more of a good-news story (for me, anyway). I'm a hobbyist with legacy mac systems and pretty much a newbie with Sage commands per se, and wanted to use the experience to get a better handle on the structure and behavior of the build system. I just hope this adds to the mac build knowledge base for Sage.</p>
<p>I've just successfully built sage-6.10 (downloaded from the git repository) on a mac book 4,1 system with a Core2Duo processor that does not upgrade MacOS beyond Snow Leopard. The total build time was about 8 hours starting with Xcode 3.2. I had difficulties getting started because all my more modern tools are in my macports installation, and I haven't installed upgrades anywhere else --- or so I thought at first. I hit upon including the path to a previous Sage installation which I did some years ago with a binary download of sage-5.13, adding the path to Sage's local/bin. And it worked!</p>
<p>I had one glitch with the installation of flint-2.5.2, when its makefile died with a request to cp -a which happened after:</p>
<pre><code>mkdir -p "./sage-6.10/local/lib"
mkdir -p "./sage-6.10/local/include/flint"
</code></pre>
<p>In my os x shell, there is no cp -a and I substituted cp -pPR by using the debug shell for the build system. Everything else went off without a hitch. What a marvelously robust build system this is, given a finicky set of standard mac build tools! Perhaps I should not find it remarkable that I can still do a build like this with a ten-or-more-year-old computer running a 12-year-old OS.</p>
<p>My question is this: I am having trouble locating solid information about which versions of Sage I should try to build for some particular version of the OS. It it just going to be a matter of dedicated experimentation? If so, my experience here tells me I am ready for that.</p>
http://ask.sagemath.org/question/47324/building-sage-on-legacy-macos-system-1058/?comment=47341#post-id-47341Thanks for the encouragement! I ended up (not surprisingly) with lots and lots (maybe 100+) of failed doctests, but much usable python code and a pretty high version of maxima (for the 10.5 platform) and many of the other goodies. I'm going to assume that builders on legacy systems should expect the doctesting problems.Thu, 01 Aug 2019 10:55:20 -0500http://ask.sagemath.org/question/47324/building-sage-on-legacy-macos-system-1058/?comment=47341#post-id-47341Comment by slelievre for <p>This isn't a question, yet, depending on replies. It's more of a good-news story (for me, anyway). I'm a hobbyist with legacy mac systems and pretty much a newbie with Sage commands per se, and wanted to use the experience to get a better handle on the structure and behavior of the build system. I just hope this adds to the mac build knowledge base for Sage.</p>
<p>I've just successfully built sage-6.10 (downloaded from the git repository) on a mac book 4,1 system with a Core2Duo processor that does not upgrade MacOS beyond Snow Leopard. The total build time was about 8 hours starting with Xcode 3.2. I had difficulties getting started because all my more modern tools are in my macports installation, and I haven't installed upgrades anywhere else --- or so I thought at first. I hit upon including the path to a previous Sage installation which I did some years ago with a binary download of sage-5.13, adding the path to Sage's local/bin. And it worked!</p>
<p>I had one glitch with the installation of flint-2.5.2, when its makefile died with a request to cp -a which happened after:</p>
<pre><code>mkdir -p "./sage-6.10/local/lib"
mkdir -p "./sage-6.10/local/include/flint"
</code></pre>
<p>In my os x shell, there is no cp -a and I substituted cp -pPR by using the debug shell for the build system. Everything else went off without a hitch. What a marvelously robust build system this is, given a finicky set of standard mac build tools! Perhaps I should not find it remarkable that I can still do a build like this with a ten-or-more-year-old computer running a 12-year-old OS.</p>
<p>My question is this: I am having trouble locating solid information about which versions of Sage I should try to build for some particular version of the OS. It it just going to be a matter of dedicated experimentation? If so, my experience here tells me I am ready for that.</p>
http://ask.sagemath.org/question/47324/building-sage-on-legacy-macos-system-1058/?comment=47340#post-id-47340Congratulations on building SageMath on this legacy macOS!Thu, 01 Aug 2019 10:36:09 -0500http://ask.sagemath.org/question/47324/building-sage-on-legacy-macos-system-1058/?comment=47340#post-id-47340