1 |
There are some other miscellaneous lam-mpi / mpich |
2 |
dependencies/conflicts/gotchas in Portage; you probably won't see them |
3 |
unless you're using ~x86 and trying to load the R packages that use |
4 |
them. When I get some free time I'll document everything in Bugzilla. |
5 |
|
6 |
Meanwhile, speaking of R, they are at R-2.2.0 and counting -- 2.3 should |
7 |
be out in the spring. Portage appears to be stuck at R-2.1.1. Is there |
8 |
any reason there hasn't been an R version bump? |
9 |
|
10 |
Donnie Berkholz wrote: |
11 |
|
12 |
> -----BEGIN PGP SIGNED MESSAGE----- |
13 |
> Hash: SHA1 |
14 |
> |
15 |
> Philippe Trottier wrote: |
16 |
> | I have stooped using mpich and started use lam-mpi take a look at |
17 |
> that ? |
18 |
> |
19 |
> That's ironic, because the lam-mpi team has stopped developing lam-mpi |
20 |
> and now works on openmpi [1], along with a number of other groups. =) |
21 |
> |
22 |
> As far as moving into the future for MPI in Gentoo goes, there's an |
23 |
> mpich2 ebuild in progress, and we'll probably start working on an |
24 |
> openmpi ebuild once they have a 1.0 release. |
25 |
> |
26 |
> Thanks, |
27 |
> Donnie |
28 |
> |
29 |
> 1. http://www.open-mpi.org/ |
30 |
> -----BEGIN PGP SIGNATURE----- |
31 |
> Version: GnuPG v1.4.2 (GNU/Linux) |
32 |
> |
33 |
> iD8DBQFDe6UHXVaO67S1rtsRAiPdAKD/G/r7DHRXymnwsoqnBzLr5xjNdgCgl7Et |
34 |
> WskpoCWoUJpddnTsm4bI2e4= |
35 |
> =/vLx |
36 |
> -----END PGP SIGNATURE----- |
37 |
|
38 |
|
39 |
-- |
40 |
M. Edward (Ed) Borasky |
41 |
|
42 |
http://linuxcapacityplanning.com |
43 |
|
44 |
-- |
45 |
gentoo-science@g.o mailing list |