Optional package openmpi-1.4.3 fails to install on Solaris 10 (SPARC) with gcc (OK with Sun compiler) #10869
Comments
This comment has been minimized.
This comment has been minimized.
|
comment:3
Its a pretty low-level C library, so I don't think Sage developers should write any documentation. We don't have documentation for libntl, say, either. You need to know MPI and write Cython code to use it. You don't necessarily need a cluster, you can also use it to distribute work over multiple cores of a single computer. Although not quite as efficient as threads, that gives you the opportunity to run your code unmodified on a cluster should you need to in the future. Since its quite a mature package I don't see a reason why it shouldn't be in optional. Most of the experimental spkgs are completely broken by comparison. I also have never seen a SPARC cluster. Though we should fix it eventually, of course. Given that Solaris uses OpenMPI as its official MPI library it must be possible to compile it :-) |
|
comment:4
Replying to @vbraun:
I can't feel that it would be better if there were some examples of how to use a cluster. If you take a look at Mathematica's documentation http://reference.wolfram.com/mathematica/ParallelTools/tutorial/Overview.html it is pretty clear about how to set up a cluster of machines. For cores on the same machine, one does not need to do anything For kernels on other machines, it's a bit more complex, but I got it set up in about 30 minutes, using a GUI where you select the kernels. It seems Sage has the OpenMPI library, but without some examples of how to use it, then it is going to be next to impossible for someone other than the people that implemented it in Sage to know how to use it. Do you know any Sage user that has used the library to do anything, who is not a developer involved in implementing it in Sage? I've got a book on OpenMPI here (got it free after reviewing another book), but I feel even if I knew how to use OpenMPI, I fear doing anything in Sage would be hard.
Same with Mathematica. The kernels can be local, remote, or a mix of the two.
Yes, it must be possible to compile it. Not sure why it does not build. I just tried the package on my OpenSolaris machine using Sun Studio, rather than gcc. That builds OK. Which probably means it would on SPARC too, though I've not tried it. I updated #10866 to indicate the library builds with the Sun compiler if using the Sun compiler. It took 9 minutes to build on my 3.33 GHz OpenSolaris machine, so I hate to think how long it would take on t2.math. It would not surprise me if it took an hour or more, as that machine is very slow. Dave |
|
comment:5
Building with the Sun compilerThis does build ok on t2.math if the Sun compiler is used However, this means the Sun C and C++ compilers are used, but the GNU Fortran compiler, One would need to manually edit the sage_fortran script to build with the Sun compiler |
sagetrac-drkirkby
mannequin
changed the title
|
comment:10
solaris tickets should be closed as outdated |
|
comment:11
ok |
Hardware & associated software
How gcc was configured on t2.math
Since the configuration of gcc is important when building Sage, this is shown. Note both the Sun linker and assembler are used.
The problem
As reported at #8522, the optional package OpenMPI package failed to install on Solaris 10 SPARC. But I will close that ticket as "wont fix" because:
Error message seen on t2.math with the latest MPI in Sage
Linker version on t2.math
Errors message seen on host 'mark' on Skynet (Solaris 10 SPARC)
Although I've not tried this myself, the errors on #8522, which are with a Sun Blade 2500, are a bit different:
So two different SPARC machines are giving different error messages with the same version of OpenMPI. This could be due to different linker versions or how different people have their systems configured.
Issues on OpenSolaris too
OpenMPI is failing to install on OpenSolaris too. That's the subject of #10866
Thoughts on OpenMPI in general
I wonder if this package should be made "experimental" rather than "optional", as it is:
CC: @sagetrac-maldun @vbraun @jhpalmieri @fchapoton @dimpase
Component: packages: optional
Issue created by migration from https://trac.sagemath.org/ticket/10869
The text was updated successfully, but these errors were encountered: