Gentoo Archives: gentoo-cluster

From: Justin Bronder <jsbronder@g.o>
To: gentoo-cluster@l.g.o
Subject: [gentoo-cluster] Re: eselect-mpi issues
Date: Fri, 13 Jun 2008 03:07:30
Message-Id: 20080613030216.GA6808@mejis.cold-front
In Reply to: [gentoo-cluster] eselect-mpi issues by Bryan Green
1 On 12/06/08 11:28 -0700, Bryan Green wrote:
2 > Hello,
3 >
4 > I'm beginning to give empi/eselect-mpi a try. Bravo, Justin, for making
5 > these!
6
7 Thanks for trying them out, I'm hoping someone else finds them as useful as I
8 have.
9
10 >
11 > I've run into one bug in eselect-mpi that effects csh users (a popular
12 > shell where I work). There is simply one setenv line that has bash syntax
13 > rather than csh syntax. I already submitted a bug: its bug 226105.
14 > Here is the patch to fix it:
15 >
16 > ================================================
17 > --- files/mpi.eselect-0.0.3 (revision 1137)
18 > +++ files/mpi.eselect-0.0.3 (working copy)
19 > @@ -161,7 +161,7 @@
20 > setenv PATH "${binpath}"
21 > setenv MANPATH "${manpath}"
22 > setenv LD_LIBRARY_PATH "${lld}"
23 > -setenv ESELECT_MPI_IMP="${1}"
24 > +setenv ESELECT_MPI_IMP "${1}"
25 > EOF
26 >
27 > echo "Remember to source ${user_ev_sh} or ${user_ev_csh}"
28 > ================================================
29
30 Fixed in eselect-0.0.3-r1. Also found another mistake when setting PATH for
31 c shells and fixed that as well.
32
33 >
34 > Also, in the README file, the for loop in step 6 is incorrect:
35 >
36 > for i in $(ls ${HOME}/.env.d/*); do
37 > source ${HOME}/.env.d/${i}
38 > done
39 >
40 > Results in:
41 >
42 > -bash: /home/bgreen/.env.d//home/bgreen/.env.d/mpi.csh: No such file or directory
43 > -bash: /home/bgreen/.env.d//home/bgreen/.env.d/mpi.sh: No such file or directoryA
44
45 Also fixed. You might also want to check out the doc I've been working on
46 lately, http://dev.gentoo.org/~jsbronder/empi.xml. Hopefully it's a little
47 more up to date.
48
49 >
50 >
51 > On the system where I'm using empi, I've created files in /etc/profile.d to
52 > source the user's .env.d files when they log in. What do you think about
53 > having the eselect-mpi ebuild install these, so mpi users dont have to do
54 > that part manually? They would instead just have to source /etc/profile or
55 > /etc/csh.login after running 'eselect mpi'.
56
57 Love it, I had not even thought of using this mechanism before even though I
58 should have. It will also simplify switching from an mpi environment to one
59 without it. I'll try to get something checked into the overlay soon,
60 shouldn't be more than a few days.
61
62 >
63 >
64 > Here are my versions of the files in /etc/profile.d:
65 >
66 > ==============
67 > mpi-config.sh
68 > ==============
69 > if [ -d ${HOME}/.env.d ]; then
70 > for i in ${HOME}/.env.d/*.sh ; do
71 > . "${i}"
72 > done
73 > unset i
74 > fi
75 >
76 > ==============
77 > mpi-config.csh
78 > ==============
79 > if ( -d ${HOME}/.env.d ) then
80 > set nonomatch
81 > foreach i ( ${HOME}/.env.d/*.csh )
82 > source ${i}
83 > end
84 > unset i nonomatch
85 > endif
86 >
87 > ==============
88 >
89 > -bryan
90
91 Thanks again for testing and your comments, they're much appreciated.
92
93 --
94 Justin Bronder

Replies

Subject Author
[gentoo-cluster] Re: eselect-mpi issues Justin Bronder <jsbronder@g.o>
Re: [gentoo-cluster] Re: eselect-mpi issues Eric Thibodeau <kyron@××××××××.com>