Re: Fwd: Problem with PATH variable and access
On Wed, 2005-10-12 at 23:42 +0300, Simo Kauppi wrote:
> Hi,
>
> On Mon, Oct 10, 2005 at 05:53:02PM -0300, Ivan Paganini wrote:
> > Sorry about the last message, I forgot to put that I am running sarge
> > 3.1stable. :-)
> >
> >
> > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > Hello all. I am not sure this is the correct place to post this, but here it
> > goes.
> > I am trying to install some scientific programs, like MPICH, ScaLAPACK, etc
> > on a PIIIx2. The installations went well, until I had to call a command or
> > library from the terminal. I have tried to set the PATH, MPI and MPI_LIB
> > variables for root and normal users (authenticated by nis), with no sucess.
> > I have put the correct lines on /etc/profile, /etc/bash.bashrc, and on
> > ~/.bashrc for normal users, and /root/.bashrc, /root/.bash_profile and
> > /root/.profile, with no sucess. The command is not found, even if the
> > variable is correctly setted. Here is an output:
> > *******************************************
> > /root/.profile:
> > MPI=/opt/gnu/mpich-1.2.7/bin
> > export MPI
> > MPI_LIB=/opt/gnu/mpich-1.2.7/lib
> > export MPI_LIB
> > PATH=$PATH:/opt/gnu/mpich-1.2.7
> >
> > /root/.bash_profile:
> > MPI=/opt/gnu/mpich-1.2.7/bin/
> > export MPI
> > MPI_LIB=/opt/gnu/mpich-1.2.7/lib/
> > export MPI_LIB
> >
> > /user/.bashrc:
> > # .bashrc
> >
> > # User specific aliases and functions
> >
> > # Source global definitions
> > if [ -f /etc/bashrc ]; then
> > . /etc/bashrc
> > fi
> >
> > MPI=/opt/gnu/mpich-1.2.7/bin
> > export MPI
> > MPI_LIB=/opt/gnu/mpich-1.2.7/lib
> > export MPI_LIB
> > PATH=$PATH:/opt/gnu/mpich-1.2.7
> >
> > /etc/profile:
> > # /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
> > # and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).
> >
> > if [ "`id -u`" -eq 0 ]; then
> > PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11"
> > else
> > PATH="/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games"
> > fi
> >
> > if [ "$PS1" ]; then
> > if [ "$BASH" ]; then
> > PS1='\u@\h:\w\$ '
> > else
> > if [ "`id -u`" -eq 0 ]; then
> > PS1='# '
> > else
> > PS1='$ '
> > fi
> > fi
> > fi
> >
> > export PATH
> >
> > umask 022
> >
> >
> >
> > ###############################
> > #Modificacoes para instalacao
> > ###############################
> >
> > ###############################
> > #MPI
> > MPI=/opt/gnu/mpich-1.2.7/bin
> > export MPI
> > MPI_LIB=/opt/gnu/mpich-1.2.7/lib
> > export MPI_LIB
> > PATH=$PATH:/opt/gnu/mpich-1.2.7
> > export PATH
> > ************************************************************
> > I already have logged and dislogged, and even rebooted the system.
> > When I issue a env, the paths are there.
> >
> > ************************************************************
> > env:
> > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/opt/gnu/mpich-
> > 1.2.7:/opt/gnu/mpich-1.2.7/
>
> I don't use MPICH, but is it possible that the command you are trying to
> execute is in /opt/gnu/mpich-1.2.7/bin directory? In that case you
> should put the whole path in your PATH variable.
>
> You can try to locate the exact path of a command with `locate
> name_of_the_command`. In general you need to provide the whole path to
> the command you want to execute; program's own bin directory is not
> automatically included in the search path.
>
> If your program has trouble finding its libraries, you might have to use
> the LD_LIBRARY_PATH variable, or put the library path into the
> /etc/ld.so.conf and run ldconfig. Like I said, I don't use MPICH, so I
> don't know if that is the case with MPICH.
>
> > PWD=/root
> > LANG=en_US
> > MPI=/opt/gnu/mpich-1.2.7/bin/
Yes, you need the mpich bin in your PATH not the mpich 'home'
I'd also recommend looking at mpich2 rather than mpich1
Reply to: