#8537: Update Open MPI package to latest - Sage version is 3 years old!
-------------------------------+--------------------------------------------
Reporter: drkirkby | Owner: tbd
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.6.2
Component: optional packages | Resolution:
Keywords: | Author: Stefan Reiterer
Upstream: N/A | Reviewer:
Merged: | Work_issues:
-------------------------------+--------------------------------------------
Changes (by maldun):
* status: needs_info => needs_review
Old description:
> Sage has an Open MPI optional package, which uses version 1.1.4 of Open
> MPI. This was released on Jan 30, 2007, so is more than 3 years old. It
> fails to build on Solaris - see #8522.
>
> The optional package is very different to most other Sage packages, which
> shows its age.
>
> * No SPKG.txt
> * No Mercurial repository
> * Sources sit in top-level directory, not in a 'src' subdirectory.
>
> I'll create a package based on the latest version of Open MPI, which is
> version 1.4.1, which was released 15th January 2010.
New description:
Sage has an Open MPI optional package, which uses version 1.1.4 of Open
MPI. This was released on Jan 30, 2007, so is more than 3 years old. It
fails to build on Solaris - see #8522.
The optional package is very different to most other Sage packages, which
shows its age.
* No SPKG.txt
* No Mercurial repository
* Sources sit in top-level directory, not in a 'src' subdirectory.
I'll create a package based on the latest version of Open MPI, which is
version 1.4.1, which was released 15th January 2010.
'''Update:''' A new spkg can be found under http://code.google.com/p/spkg-
upload/downloads/detail?name=openmpi-1.4.3.spkg
--
Comment:
Replying to [comment:8 vbraun]:
> Thanks for updating everything!
>
> I think you should be using `rm -f` to delete the old versions. The
current `spkg-install` will fail to install if you don't already have the
old openmpi lying around.
>
> You should always use `$MAKE` because somebody might have set
`MAKE=/path/gnu-make` or so. Do you need to disable parallel make? Then
set `MAKE="$MAKE -j 1"`
>
> Does mpi4py or anything else need the fortran API? If no, why not
disable it in the configure. If yes, is there any way we can make it call
`sage_fortran` as the compiler?
>
Thanks for all the information!
I changed everything to your advices. rm worked without -f but I added it
just to be sure.
Also found an unnecessary rm statement. The fortran things were already
outcommented but I removed them completely, to avoid confusion.
I upload a the new spkg-install to see the difference
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8537#comment:9>
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.
