On Thu, Jan 26, 2012 at 12:52 PM, Christopher Swenson <ch...@caswenson.com> wrote: > -1 for distributing our own version of gcc. > > As someone who has been peripherally involved with this sort of thing at > Google, here are some downsides: > > 1) several hours of extra compiling and testing (a full boostrap build of > GCC can be very painful, and running every test can take a very long time)
We're not including it with Sage. We would make it available since XCode is such a pain in the ass (and is not free). That Cython and even "sage -b" don't work without having to pay Apple additional money, gets in the way of our goals for Sage. > 2) you are going to have to start throwing more and more things into spkgs > as other things break (binutils comes to mind) That's why we are here. > 3) you *still* have to have a C compiler already on the system to compile > the stupid thing anyway :) That's only on the system that we build the package on. No users will need that C compiler. Given that the main issue we are trying to address is installing the right compiler, I don't see this as a problem. Also, it will be nice since we can include gfortran in our gcc spkg, and completely remove the binary fortran spkg from Sage. > 4) people will constantly ask why you didn't choose clang + llvm No choice has been made. So far I have a choice of zero working options. When I have >= 2, I can make a choice. > 5) why don't you choose clang + llvm? :-) > > --Christopher > > > On Thu, Jan 26, 2012 at 15:15, William Stein <wst...@gmail.com> wrote: >> >> Hi, >> >> Earlier today I was arguing that we need to support Xcode 4.x, etc., >> in the context of the PARI bugs. >> >> I'm sitting here with a grad student with a solid Mac running OS X >> 10.6.8, and trying to get XCode 3.x on it is HELL. >> None of our Apple ID's work for the Developer network, etc. We can't >> find a download. Anyway, it is frustrating. >> The App store only supports 4.x. >> >> I'm just curious if anybody has looked into the possibility of us >> distributing our own build of GCC, which is good enough to build Sage >> and use Cython. >> >> Incidentally, the only reason he needs XCode is because our "sage -b" >> build system is really stupid. If you do >> >> "sage -b" >> >> and don't have a compiler, it will die, even if you aren't doing >> anything with Cython. He just wants to write some .py files. >> >> http://trac.sagemath.org/sage_trac/ticket/12365 >> >> >> -- William >> >> -- >> 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 > > > -- > 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
