#6453: [with patch, needs review] MPFR test failures on Solaris 10 update 4 on
host 't2'
----------------------+-----------------------------------------------------
Reporter: drkirkby | Owner: drkirkby
Type: defect | Status: assigned
Priority: major | Milestone: sage-4.1.1
Component: solaris | Keywords: compiler bug
Reviewer: | Author: Paul Zimmermann, David Kirkby
Merged: |
----------------------+-----------------------------------------------------
Comment(by drkirkby):
I updated the package changing just some text, which appeared to have
caused some confusion to a potential reviewer. In particular, I did not
enable any checks in MPFR - they were already enabled. So my patch will
not slow the build process.
Previously I posted outputs from my own Sun Blade 2000 computer, which is
a sun4u architecture and so did NOT need patching.
{{{
$ make
<SNIP>
Since this is not a sun4v system, the MPFR binary will not
be patched
WARNING: Problems may occur if you try to run this SPARC
binary on a sun4v system (T1, T2 or T2+ processors). Binaries created like
this should not distributed unless you know the end users system will not
be sun4v. Set INCLUDE_MPFR_PATCH to 1, to include the patch, if you are
unsure.
}}}
Here's the default output seen on 't2' with this new patch:
{{{
$ make
<SNIP>
This is a sun4v system, so the MPFR library will be patched. The binaries
should run correctly on any SPARC system whose operating system is
no older than the system used to build the binaries.
}}}
Notice how it differs from that on my own machine ? Here's the output from
'uname' and 'arch -k' on both my Sun Blade 2000 (kestrel) and a Sun T5240
(t2)
First 't2'
{{{
kir...@t2:[~] $ uname -a
uname -a
SunOS t2 5.10 Generic_141414-02 sun4v sparc SUNW,T5240
kir...@t2:[~] $ arch -k
arch -k
sun4v
}}}
now my home machine 'kestrel', which is actually a Blade 2000, not a Blade
1000 as the output says. The two machines share the same motherboard.
{{{
drkir...@kestrel:[~] $ arch -k
sun4u
drkir...@kestrel:[~] $ uname -a
SunOS kestrel 5.10 Generic_139555-08 sun4u sparc SUNW,Sun-Blade-1000
}}}
* Sun Blade 2000 ('kestrel') has a sun4u architecture, so does not need
patching
* Sun T5240 ('t2') has a sun4v architecture, so does need patching
On either system it is possible to override the default.
I've put the code in /tmp/kirkby/sage-4.1/ on 't2' and changed the
permissions of all files so any user can write to them. It will allow
testing by others. (Of course it could break too, if two people start
testing together, but that is a risk I will take).
It should be noted that were are not really any closer to solving this, as
at least 4 explanations have been given by different people:
* It's an MPFR bug
* It's an MPIR bug
* It's a gcc bug
* It's a bug in the Solaris implementation of memset on sun4v systems.
Note, although I don't believe there is any plans to support Solaris 9, I
don't actually see why Sage should not work on a Solaris 9 system. A
Solaris 9 system could be using the even older sun4m architecture.
Although I've not checked it, the updated .spkg file should work on that
too, but will not apply the patch by default.
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6453#comment:9>
Sage <http://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
-~----------~----~----~----~------~----~------~--~---
