On 9/7/07, Hamptonio <[EMAIL PROTECTED]> wrote:
> I am hoping to use sage on some supercomputers and/or clusters.
> Currently I am trying to compile it on the IBM Power4 machine at the
> Minnesota Supercomputing Center (see http://www.msi.umn.edu/power4/index.html
> for some details on that).   Its about 300 Power4 processors running
> AIX.

Porting SAGE to a new architecture / operating system is a
potentially difficult project, that should not
be underestimated.  Nobody has ever compiled SAGE
(or probably many of its components) under AIX, so I predict
based on experience that the number of problems that one
would have will be at least enough to keep 2 or 3 very very
smart people occupied for several weeks, and maybe more.
In short, SAGE isn't supported on AIX or Power4,
and isn't likely to be unless several SAGE developers had
access to such a machine -- then it probably would get
supported there.   I of course really really wish SAGE were
supported on a wider range of machines, especially those
used in supercomputing (!)

> I just tried compiliing sage-2.8.3.6 on it, and it started off OK but
> failed while compiling libgcrypt.  It seems this is often a difficult
> package, since it looks like a sticking point on Solaris and cygwin as
> well.  Is there a  way to build around that? Would it help to try an
> earlier sage version?

If a package called foo.spkg won't build, if you do
   touch spkg/installed/foo
then type "make" the build will continue as if the package
did build successfully.

One can fully build SAGE without libgcrypt or any of the gnutls stuff.
It will work -- the only thing that might fail is the notebook, but
then only in secure mode.

William

--~--~---------~--~----~------------~-------~--~----~
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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to