Find the answer to your Linux question:
Results 1 to 2 of 2
I have a strange problem with Fortran 10.1.008 ... the script doens't work. [root@nemunas ~]# $PATH -bash: /opt/gridengine/bin/lx26-ia64:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/java/j2sdk1.4.2_06//bin:/opt/intel/itc60/bin:/opt/intel/ita60/bin :/opt/intel/fc/10.1.008 /bin:/opt/intel/cc/10.1.008/bin:/opt/globus/bin:/opt/globus/sbin:/opt/intel/cc/10.1.008/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/opt/apache-ant/bin:/opt/ganglia/bin:/opt/lam/gnu/bin:/opt/maui/bin:/opt/torque/bin:/opt/torque/sbin:/opt/rocks/bin:/opt/rocks/sbin:/root/bin: No such file or directory [root@nemunas ~]# ifortvars.sh [root@nemunas ~]# ...
  1. #1
    Just Joined!
    Join Date
    May 2006
    Posts
    3

    problem with Fortran 10.1.008 ... script doens't work

    I have a strange problem with Fortran 10.1.008 ... the script doens't work.

    [root@nemunas ~]# $PATH
    -bash: /opt/gridengine/bin/lx26-ia64:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/java/j2sdk1.4.2_06//bin:/opt/intel/itc60/bin:/opt/intel/ita60/bin:/opt/intel/fc/10.1.008/bin:/opt/intel/cc/10.1.008/bin:/opt/globus/bin:/opt/globus/sbin:/opt/intel/cc/10.1.008/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/opt/apache-ant/bin:/opt/ganglia/bin:/opt/lam/gnu/bin:/opt/maui/bin:/opt/torque/bin:/opt/torque/sbin:/opt/rocks/bin:/opt/rocks/sbin:/root/bin: No such file or directory

    [root@nemunas ~]# ifortvars.sh
    [root@nemunas ~]#

    [root@nemunas ~]# cat /etc/profile.d/ifortvars.sh
    #! /bin/bash

    if [ -z "${PATH}" ]
    then
    PATH="/opt/intel/fc/10.1.008/bin"; export PATH
    else
    PATH="/opt/intel/fc/10.1.008/bin:$PATH"; export PATH
    fi

    if [ -z "${LD_LIBRARY_PATH}" ]
    then
    LD_LIBRARY_PATH="/opt/intel/fc/10.1.008/lib"; export LD_LIBRARY_PATH
    else
    LD_LIBRARY_PATH="/opt/intel/fc/10.1.008/lib:$LD_LIBRARY_PATH"; export LD_LIBRARY_PATH
    fi

    if [ -z "${MANPATH}" ]
    then
    MANPATH="/opt/intel/fc/10.1.008/man":$(manpath); export MANPATH
    else
    MANPATH="/opt/intel/fc/10.1.008/man:${MANPATH}"; export MANPATH
    fi

    if [ -z "${INTEL_LICENSE_FILE}" ]
    then
    INTEL_LICENSE_FILE="/opt/intel/fc/10.1.008/licenses:/opt/intel/licenses:${HOME}/intel/licenses"; export INTEL_LICENSE_FILE
    else
    INTEL_LICENSE_FILE="${INTEL_LICENSE_FILE}:/opt/intel/fc/10.1.008/licenses:/opt/intel/licenses:${HOME}/intel/licenses"; export INTEL_LICENSE_FILE
    fi


    [root@nemunas ~]# /opt/intel/fc/10.1.008/bin/ifortvars.sh
    [root@nemunas ~]#
    Any ideas?

  2. #2
    Linux Engineer wje_lf's Avatar
    Join Date
    Sep 2007
    Location
    Mariposa
    Posts
    1,192
    You execute that file by its base name on the command line, then you show us its contents, then you execute that file by its full path name on the command line again. Neither of those will do what you want because of exactly how you ran them (more details on this if you want, just ask). But then, neither of those is necessary, because you had already placed the command in your /etc/profile.d, and (as you helpfully highlighted in bold for us) the script worked, or at least the part that modified your $PATH.

    It may not seem to have worked because you did this on the command line:
    Code:
    $PATH
    That does not merely display $PATH; instead it tries to run $PATH as a command. It does show you $PATH, but only as an ugly error message.

    A better way to see what $PATH is would be to do this at the command line:
    Code:
    echo $PATH
    Hope this helps.
    --
    Bill

    Old age and treachery will overcome youth and skill.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...