On Mon, Dec 8, 2008 at 4:35 AM, bourbabis <[EMAIL PROTECTED]> wrote:
>
> Hello.
>
> OK, you're probably right, it's a hardware problem. It's the
> most credible explanation, even if the exact circumstances
> triggering it will remain obscure. I will follow your suggestions
> and try a step by step compilation, following the script.
>
> Just a precision, this is not I absolutely *want* to compile Sage,
> but unfortunately I have no choice because there is no suitable
> binary. The Sage version I currently use (2.11) was compiled by
> the Sage team, I've never succeed to complete a compilation.

I made that binary on meccah.math.harvard.edu.  Unfortunately, that
machine was turned off and "tossed" (?) several months ago, since it
was vintage early 2001 and was using up lots of valuable space.   I
now do not have access to any computers that do not have sse* support,
so can't build
a binary for you.

It would be interesting to figure out how to build binaries on
sage.math that don't require SSE.   I have no clue how to do this?
Does anybody have any ideas?

After searching around for a while, my best idea is to ask Clint
Whaley how to build Atlas in such a way that it doesn't use SSE, even
if SSE is available.  I was not able to figure this out from the docs
or config script.

Wiliam

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to