#11331: PolyBoRi won't build on OS X 10.4 PPC G4
------------------------------+---------------------------------------------
Reporter: kcrisman | Owner: AlexanderDreyer
Type: defect | Status: positive_review
Priority: major | Milestone: sage-4.7.1
Component: build | Keywords:
Work_issues: | Upstream: Fixed upstream, in a later
stable release.
Reviewer: Georg S. Weber | Author: Alexander Dreyer
Merged: | Dependencies:
------------------------------+---------------------------------------------
Changes (by GeorgSWeber):
* status: needs_review => positive_review
* reviewer: => Georg S. Weber
Comment:
Hi,
what a nice "ready-to-go" new spkg and "p3-vs-p2" patch, presented on "a
silver tablet" --- I just couldn't resist!
Both my MacIntel and my MacPPC systems use OS X 10.4.11 with XCode 2.5
(the MacIntel has a Core2Duo CPU with 2 GHz and 2 GB RAM, the MacPPC has
an older G4 CPU with 550 MHz and 768 MB RAM). These are the findings from
my side (all one-time tries only):
- On my MacIntel with Sage-4.7.alpha4 (and polybori-0.7.0.p2), building
from scratch went fine, but with Sage-4.7.rc2 (and the very same
polybori-0.7.0.p2), building from scratch broke with the described
internal compiler error.
- On my MacPPC with Sage-4.7.rc2 (and still polybori-0.7.0.p2), building
from scratch went fine(!!).
So the issue of this ticket firstly does not seem to hit in 100% of the
cases, and secondly seems to affect both the MacIntel and MacPPC platforms
...
I updated on both systems the Sage-4.7.rc2 install with the new
polybori-0.7.0.p3 spkg of this ticket, and on both systems they did build
fine. On the MacIntel, "make testlong" finished in the meantime, and
passed fine (except for the known old "maxima.py" issue, which is
unrelated).
The SPKG.txt is updated correctly, even the mercurial repository looks
good, excellent! The only downside might be that the problem still lurks,
since only more testing really could give confidence. But the best way to
achieve the latter is to drop this spkg in the mainline code base, which
is justified, because regressions are hardly to be awaited from looking at
the tiny (and very local) changes.
All in all: positive review.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11331#comment:15>
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.
