From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1K80kq-0007Kv-9t for garchives@archives.gentoo.org; Sun, 15 Jun 2008 22:31:21 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 00272E0499; Sun, 15 Jun 2008 22:31:19 +0000 (UTC) Received: from kyron.neuralbs.com (modemcable086.140-70-69.static.videotron.ca [69.70.140.86]) by pigeon.gentoo.org (Postfix) with ESMTP id D6A92E0499 for ; Sun, 15 Jun 2008 22:31:18 +0000 (UTC) Received: from [192.168.1.2] (kyron.neuralbs.com [192.168.1.2]) by kyron.neuralbs.com (Postfix) with ESMTP id 9B24D3913F for ; Sun, 15 Jun 2008 18:31:18 -0400 (EDT) Message-ID: <48559836.7070302@neuralbs.com> Date: Sun, 15 Jun 2008 18:31:18 -0400 From: Eric Thibodeau Organization: Neural Bucket Solutions Inc. User-Agent: Thunderbird 2.0.0.14 (X11/20080525) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-cluster@lists.gentoo.org Reply-to: gentoo-cluster@lists.gentoo.org MIME-Version: 1.0 To: gentoo-cluster@lists.gentoo.org Subject: Re: [gentoo-cluster] Re: eselect-mpi issues References: <20080612182855.17D522395D0@ece06.nas.nasa.gov> <20080613030216.GA6808@mejis.cold-front> In-Reply-To: <20080613030216.GA6808@mejis.cold-front> Content-Type: multipart/alternative; boundary="------------020804010308060605080703" X-Archives-Salt: 404a0a85-2bda-495a-b9a3-ae5bf5ed403c X-Archives-Hash: 81e510be03a95425a3dd0aadd65b04b2 This is a multi-part message in MIME format. --------------020804010308060605080703 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Justin Bronder wrote: > On 12/06/08 11:28 -0700, Bryan Green wrote: > >> Hello, >> >> I'm beginning to give empi/eselect-mpi a try. Bravo, Justin, for making >> these! >> > > Thanks for trying them out, I'm hoping someone else finds them as useful as I > have. > It is planned to be part of the Gentoo Clustering LiveCD ;) > >> 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}" >> ================================================ >> > > Fixed in eselect-0.0.3-r1. Also found another mistake when setting PATH for > c shells and fixed that as well. > > >> 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 directoryA >> > > Also fixed. You might also want to check out the doc I've been working on > lately, http://dev.gentoo.org/~jsbronder/empi.xml. Hopefully it's a little > more up to date. > Have to remember that one ;) > >> 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'. >> > > Love it, I had not even thought of using this mechanism before even though I > should have. It will also simplify switching from an mpi environment to one > without it. I'll try to get something checked into the overlay soon, > shouldn't be more than a few days.< > Keep us posted because I will definitely want that version! > >> 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 >> > > Thanks again for testing and your comments, they're much appreciated. > Yeah, thanks you both, multi-mpi-on-1-system has always plagued me too ;) --------------020804010308060605080703 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Justin Bronder wrote: 
On 12/06/08 11:28 -0700, Bryan Green wrote:
  
Hello,

I'm beginning to give empi/eselect-mpi a try.  Bravo, Justin, for making
these!
    

Thanks for trying them out, I'm hoping someone else finds them as useful as I
have.
It is planned to be part of the Gentoo Clustering LiveCD ;)
  
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}"
================================================
    

Fixed in eselect-0.0.3-r1.  Also found another mistake when setting PATH for
c shells and fixed that as well.

  
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 directoryA
    

Also fixed.  You might also want to check out the doc I've been working on
lately, http://dev.gentoo.org/~jsbronder/empi.xml.  Hopefully it's a little
more up to date.
Have to remember that one ;)
  
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'.
    

Love it, I had not even thought of using this mechanism before even though I
should have.  It will also simplify switching from an mpi environment to one
without it.  I'll try to get something checked into the overlay soon,
shouldn't be more than a few days.<
Keep us posted because I will definitely  want that version!
  
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
    

Thanks again for testing and your comments, they're much appreciated.
Yeah, thanks you both, multi-mpi-on-1-system has always plagued me too ;)
--------------020804010308060605080703-- -- gentoo-cluster@lists.gentoo.org mailing list