On 2012-05-24, William Stein <wst...@gmail.com> wrote: > On Thu, May 24, 2012 at 8:38 AM, Jason Ekstrand <ja...@jlekstrand.net> wrote: >> Jason, >> I'll get back to you on the details in a few days when I actually have >> a mac sitting on my desk to test with. I guess the next question is, >> If you have to have command line tools installed anyway, why are we >> bundling gcc? > > Apple's compilers are buggy. > > Also, before I could install the OS X command line tools, I had to > first install XCode. People keep suggesting on this thread that the > command line tools are currently an *alternative* to XCode, but for me > at least that did not seem to be the case.
my suggestion about Xcode-less way was based on what I read on the net, and on the sqrt5.cs experience, as that machine did not have XCode installed, AFAIK. And again, it could be a moving target, i.e. what didn't work on 10.7.n works on 10.7.n+1 Sorry if it confused anyone. Dima > > -- William > >> --Jason >> >> >> >> On Thu, May 24, 2012 at 10:32 AM, Jason Grout >> <jason-s...@creativetrax.com> wrote: >>> On 5/24/12 9:45 AM, Jason Ekstrand wrote: >>>> >>>> Here is the problem: Sage 5 ships with GCC bundled in so that mac >>>> users can install sage and build sage packages without having to have >>>> the mac build toolchain (It makes sage much easier to install for the >>>> end user). There is a problem in the way it was bundled (specifically >>>> regarding limits.h and possibly others) that prevents it from building >>>> certain C extensions (i.e. Jason Grout's Minimum Rank library). These >>>> problems probably have not come into light before because everyone who >>>> has tested the bundle is a developer and so they already have the dev >>>> tools installed. If I'm misunderstanding the purpose of bundling GCC >>>> into sage 5, please let me know. >>> >>> >>> >>> Georg's message indicates that you *do* need the OSX command line tools >>> installed to get the system headers (which would be necessary for compiling >>> extensions). So then the question is: do you have the OSX command line >>> tools installed (which is a different question than if you have XCode >>> installed). >>> >>> In other words, if I understand Georg and Dima correctly, the answer to your >>> original question: >>> >>> >>> "It appears as if the version of the limits.h file bundled in with sage >>> depends on the system's limits.h file which does not exist on a standard >>> MacOS 10.7 install. How do you recommend dealing with this?" >>> >>> is: Install the OSX command line tools (not XCode), which include such a >>> header file. >>> >>> Disclaimer: I don't have 10.7, so I can't test my answer above. >>> >>> Thanks, >>> >>> Jason >>> >>> >>> >>> -- >>> 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 >> >> -- >> 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 > > > > -- > William Stein > Professor of Mathematics > University of Washington > http://wstein.org > -- 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
