I seem to be unable to build Sage on 10.7, so I'm checking my configuration against what you guys know to work.
I am running 10.7.1, with Xcode Version 4.2.1 (4D502). The beta4 release does not even get started for me (the prereq script objects to Xcode 4).
Thanks!!
-- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds ----------- I'm beginning to like the cut of his jibberish. -----------
On Sunday, February 19, 2012 1:18:44 PM UTC-8, Justin C. Walker wrote:
> I seem to be unable to build Sage on 10.7, so I'm checking my > configuration against what you guys know to work.
> I am running 10.7.1, with Xcode Version 4.2.1 (4D502). The beta4 release > does not even get started for me (the prereq script objects to Xcode 4).
There is a thread about building Sage in OS X 10.7 in sage-devel. One method which works for me, as reported there:
- download http://sage.math.washington.edu/home/jdemeyer/release/sage-5.0.beta4-... rather than the usual beta4 - upgrade to Xcode 4.3. - run Xcode, choose "Preferences" from the File menu, then choose the "Download" tab, and install the "Command Line Tools". - from the terminal, run "sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer".
(Another method, which seems to work on some machines but not others: just do the first step above and then do "export CC=clang" and "export CXX=clang++".)
Then "make ptestlong" should work. If you do "export SAGE_CHECK=yes", cvxopt will fail self-tests, as will python (as usual), but everything else should work.
If you could follow up in the sage-devel thread, that might be best.
On Feb 19, 2012, at 15:02 , John H Palmieri wrote:
> On Sunday, February 19, 2012 1:18:44 PM UTC-8, Justin C. Walker wrote: >> I seem to be unable to build Sage on 10.7, so I'm checking my configuration against what you guys know to work. >> I am running 10.7.1, with Xcode Version 4.2.1 (4D502). The beta4 release does not even get started for me (the prereq script objects to Xcode 4). > There is a thread about building Sage in OS X 10.7 in sage-devel. One method which works for me, as reported there:
> - download http://sage.math.washington.edu/home/jdemeyer/release/sage-5.0.beta4-... rather than the usual beta4 > - upgrade to Xcode 4.3. > - run Xcode, choose "Preferences" from the File menu, then choose the "Download" tab, and install the "Command Line Tools". > - from the terminal, run "sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer".
> (Another method, which seems to work on some machines but not others: just do the first step above and then do "export CC=clang" and "export CXX=clang++".)
> Then "make ptestlong" should work. If you do "export SAGE_CHECK=yes", cvxopt will fail self-tests, as will python (as usual), but everything else should work.
> If you could follow up in the sage-devel thread, that might be best.
Following up as requested on this list:
Upgrading to Xcode 4.3 doesn't work for me: I am still on 10.7.1, and would prefer not to upgrade to 10.7.3 (which is required). Has anyone succeeded with my configuration (above)?
I've tried the 'CC=clang' trick, but that seems to run aground on the 'prereq' spkg-install check (if Xcode's version is 4.x or greater, complain and stop).
Justin
-- Justin C. Walker, Curmudgeon-at-Large () The ASCII Ribbon Campaign /\ Help Cure HTML Email
On Sunday, February 19, 2012 4:00:05 PM UTC-8, Justin C. Walker wrote:
> On Feb 19, 2012, at 15:02 , John H Palmieri wrote:
> > On Sunday, February 19, 2012 1:18:44 PM UTC-8, Justin C. Walker wrote: > >> I seem to be unable to build Sage on 10.7, so I'm checking my > configuration against what you guys know to work. > >> I am running 10.7.1, with Xcode Version 4.2.1 (4D502). The beta4 > release does not even get started for me (the prereq script objects to > Xcode 4).
> > There is a thread about building Sage in OS X 10.7 in sage-devel. One > method which works for me, as reported there:
> > - download > http://sage.math.washington.edu/home/jdemeyer/release/sage-5.0.beta4-... than the usual beta4 > > - upgrade to Xcode 4.3. > > - run Xcode, choose "Preferences" from the File menu, then choose the > "Download" tab, and install the "Command Line Tools". > > - from the terminal, run "sudo xcode-select -switch > /Applications/Xcode.app/Contents/Developer".
> > (Another method, which seems to work on some machines but not others: > just do the first step above and then do "export CC=clang" and "export > CXX=clang++".)
> > Then "make ptestlong" should work. If you do "export SAGE_CHECK=yes", > cvxopt will fail self-tests, as will python (as usual), but everything else > should work.
> > If you could follow up in the sage-devel thread, that might be best.
> Following up as requested on this list:
> Upgrading to Xcode 4.3 doesn't work for me: I am still on 10.7.1, and > would prefer not to upgrade to 10.7.3 (which is required). Has anyone > succeeded with my configuration (above)?
> I've tried the 'CC=clang' trick, but that seems to run aground on the > 'prereq' spkg-install check (if Xcode's version is 4.x or greater, complain > and stop).
The complaint might have said "export the variable SAGE_PORT to something non-empty". That's what you should do.
> It would be interesting to have more OS X 10.7 results. So, could you > please try: > $ SAGE_PORT=yes MAKE="make -j1" make
> Then, in a separate directory a second Sage build with: > $ SAGE_PORT=yes CC=clang MAKE="make -j1" make
> In all cases, success or not, please send me spkg/logs/gcc-4.6.2.log
Both builds blew up in the build of MPIR.
I'm sending you a tarball containing the GCC and MPIR logs for each, direct to you.
Justin
-- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds ----------- Like the ski resort full of girls hunting for husbands and husbands hunting for girls, the situation is not as symmetrical as it might seem. - Alan MacKay --
