#11881: Metaticket: build Sage on OS X 10.7 Lion
--------------------------+-------------------------------------------------
Reporter: jhpalmieri | Owner: GeorgSWeber
Type: defect | Status: new
Priority: blocker | Milestone: sage-5.0
Component: build | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
--------------------------+-------------------------------------------------
Comment(by was):
Replying to [comment:46 jdemeyer]:
> I am currently at the PARI atelier and we're discussing OS X Lion.
Essentially the PARI developers are
> saying that Apple's compiler is completely broken
True, but Apple's compiler has a few bugs (like any optimizing compiler),
which in the 6 million lines of code that gets compiled results in -- as
far we can tell from our tests -- exactly two issues with two very tightly
coded C/C++ programs: PARI and Symmetrica. To say that the entire
compiler is "completely broken" is perhaps overstating things a little
bit.
> and that the Only Right Solution is to install a real compiler, i.e.
gcc.
Has the compiler bug been reported upstream yet? I think we should:
1. report the bug upstream
2. lower the optimization level when compiling the relevant parts of
PARI and Symmetrica.
In my experience, 2 will have a barely noticeable impact on performance
for most users. In fact, I've been using sage-5.0 compiled from scratch
with Apple's compiler on my laptop for the last week, and never noticed
that PARI is -O0.
Moreover, I think there is potentially a lot of value in the fact that we
can build Sage using both standard GCC and this LLVM thing:
gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2335.15.00)
This will increase our code robustness in the long run, and may provide
new debuging tools, etc.
> Power users who need Pari optimized would be expected to have the
technical know-how to use the right one,
I'm such a user and I don't want to have to build GCC from source.
> It's certainly better than telling people they can't compile Sage at
all, and your point
> about the binaries is naturally spot-on.
(1) Cython and (2) making it so any user with a standard compiler can do
full development on Sage, is critical functionality of Sage in my opinion.
If we don't support XCode 4.x at all, then we aren't supported (1) and
(2).
Jereon, I personally hope you can convince Bill and Karim to report the
compiler bug to Apple. They are in the best position to do so, since they
could probably isolate the problem better than any of us. Apple
regularly upgrades their devel tools and pushes out the updates. If this
had been reported to Apple back in August 2011 when this was on the PARI
list, maybe it would be fixed now. Obviously, if they don't have access
to OS X 10.7 that's a nonstarter. I'm on campus more right now, so I can
probably setup sqrt5.cs.washington.edu again so they will have 10.7
accounts. Let me know if that would make a big difference. Maybe
this whole problem is my fault due to sqrt5.cs.washington.edu not being
robust.
-- william
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11881#comment:51>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
