From: Bryan Green <bryan.d.green@nasa.gov>
To: gentoo-cluster@lists.gentoo.org
Subject: [gentoo-cluster] eselect-mpi issues
Date: Thu, 12 Jun 2008 11:28:55 -0700 [thread overview]
Message-ID: <20080612182855.17D522395D0@ece06.nas.nasa.gov> (raw)
Hello,
I'm beginning to give empi/eselect-mpi a try. Bravo, Justin, for making
these!
I've run into one bug in eselect-mpi that effects csh users (a popular
shell where I work). There is simply one setenv line that has bash syntax
rather than csh syntax. I already submitted a bug: its bug 226105.
Here is the patch to fix it:
================================================
--- files/mpi.eselect-0.0.3 (revision 1137)
+++ files/mpi.eselect-0.0.3 (working copy)
@@ -161,7 +161,7 @@
setenv PATH "${binpath}"
setenv MANPATH "${manpath}"
setenv LD_LIBRARY_PATH "${lld}"
-setenv ESELECT_MPI_IMP="${1}"
+setenv ESELECT_MPI_IMP "${1}"
EOF
echo "Remember to source ${user_ev_sh} or ${user_ev_csh}"
================================================
Also, in the README file, the for loop in step 6 is incorrect:
for i in $(ls ${HOME}/.env.d/*); do
source ${HOME}/.env.d/${i}
done
Results in:
-bash: /home/bgreen/.env.d//home/bgreen/.env.d/mpi.csh: No such file or directory
-bash: /home/bgreen/.env.d//home/bgreen/.env.d/mpi.sh: No such file or directory
On the system where I'm using empi, I've created files in /etc/profile.d to
source the user's .env.d files when they log in. What do you think about
having the eselect-mpi ebuild install these, so mpi users dont have to do
that part manually? They would instead just have to source /etc/profile or
/etc/csh.login after running 'eselect mpi'.
Here are my versions of the files in /etc/profile.d:
==============
mpi-config.sh
==============
if [ -d ${HOME}/.env.d ]; then
for i in ${HOME}/.env.d/*.sh ; do
. "${i}"
done
unset i
fi
==============
mpi-config.csh
==============
if ( -d ${HOME}/.env.d ) then
set nonomatch
foreach i ( ${HOME}/.env.d/*.csh )
source ${i}
end
unset i nonomatch
endif
==============
-bryan
--
gentoo-cluster@lists.gentoo.org mailing list
next reply other threads:[~2008-06-12 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 18:28 Bryan Green [this message]
2008-06-12 19:04 ` [gentoo-cluster] eselect-mpi issues Bryan Green
2008-06-13 3:02 ` [gentoo-cluster] " Justin Bronder
2008-06-15 19:40 ` Justin Bronder
2008-06-15 22:31 ` Eric Thibodeau
2008-06-20 20:51 ` Alexey Shvetsov
2008-06-27 4:09 ` Eric Thibodeau
2008-06-27 5:50 ` Alexey Shvetsov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080612182855.17D522395D0@ece06.nas.nasa.gov \
--to=bryan.d.green@nasa.gov \
--cc=gentoo-cluster@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox