On Tue, Feb 21, 2012 at 14:00, entropy <jberw...@gmail.com> wrote: > John, > > Just to confirm, did this build work for you on Lion 10.7.2, with > Xcode 4.3, and gcc version 4.2.1 (LLVM build 2336.9.00)? From you > follow-up messages I am assuming that beta4-gcc still builds a copy of > gcc-4.6 on top of everything else, correct?
Yup, this is correct. > > I never was able to get clang to build sage on my Apple (10.7.2 with > Xcode 4.2). Just to make sure, you were using the gcc version of sage, yes? There are some components of sage that rely on gnu extensions, so currently gcc is needed, however you should be able to build the bundled version of gcc+deps with clang. > I was wondering if a few of you who were able to > successfully build sage on your Mac could chime in with your "uname - > a" as well as Xcode and gcc versions. I'm on > > $ uname -a > Darwin hyperion 11.3.0 Darwin Kernel Version 11.3.0: Thu Jan 12 > 18:47:41 PST 2012; root:xnu-1699.24.23~1/RELEASE_X86_64 x86_64 > > with > $ gcc --version > i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. > build 5658) (LLVM build 2335.15.00) > > and Xcode version 4.1. Would you mind giving clang --version as well (I only tested on Xcode 4.2 and am currently testing with the freely released command line tools that were released alongside 4.3). > > Thanks, > Jesse > > > On Feb 19, 12:53 am, John H Palmieri <jhpalmier...@gmail.com> wrote: >> On Saturday, February 18, 2012 3:12:19 PM UTC-8, John H Palmieri wrote: >> >> > We have another small problem with Lion. I just wiped my hard drive and >> > reinstalled Lion (because of some non-Sage related issues). Then I >> > reinstalled Xcode: the newly released version 4.3. Two issues: >> > command-line tools are no longer installed by default, so you have to >> > install gcc, clang, etc., by running Xcode, choosing "Preferences", >> > clicking the "Downloads" tab, and installing "Command Line Tools". Next, >> > there is now no longer a /Developer directory, which means that the command >> > xcodebuild (which is run by the prereq script) may fail to report the >> > correct version of Xcode. So from the shell, you need to run >> >> > $ xcode-select -switch /Applications/Xcode.app/Contents/Developer >> >> > (and you may need to run this via sudo). So these instructions need to be >> > added to the installation guide or the README.txt file. >> >> > For the second issue, it might instead be better to figure out the version >> > of Xcode some other way in the prereq script (and anywhere else this is >> > done, like maybe the current python spkg). >> >> > This version of Xcode has new versions of gcc and clang, so I'm trying to >> > compile with those to see if it makes any difference. >> >> On the plus side, on the laptop where I had problems before, Sage built and >> passed all doctests using the default compiler: >> >> $ gcc --version >> i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build >> 5658) (LLVM build 2336.9.00) >> Copyright (C) 2007 Free Software Foundation, Inc. >> This is free software; see the source for copying conditions. There is NO >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >> >> I'm going to build with SAGE_CHECK=yes to see what packages fail >> self-tests, but Apple seems to have fixed some of their compiler bugs in >> this latest release. >> >> -- >> John > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org -- Andrew -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
