Where is LD_LIBRARY_PATH and PATH?











up vote
1
down vote

favorite












I type echo $LD_LIBRARY_PATH and got /usr/local/cuda-9.0/lib64 but when I check my bashrc file they are not there. Where are they ?



# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color|*-256color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi

if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}[33[01;32m]u@h[33[00m]:[33[01;34m]w[33[00m]$ '
else
PS1='${debian_chroot:+($debian_chroot)}u@h:w$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="[e]0;${debian_chroot:+($debian_chroot)}u@h: wa]$PS1"
;;
*)
;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'

alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi

# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands. Use like so:
# sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '''s/^s*[0-9]+s*//;s/[;&|]s*alert$//''')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
fi

# added by Anaconda3 installer
export PATH="/home/kong/anaconda3/bin:$PATH"
120,1 Bot









share|improve this question


























    up vote
    1
    down vote

    favorite












    I type echo $LD_LIBRARY_PATH and got /usr/local/cuda-9.0/lib64 but when I check my bashrc file they are not there. Where are they ?



    # ~/.bashrc: executed by bash(1) for non-login shells.
    # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
    # for examples

    # If not running interactively, don't do anything
    case $- in
    *i*) ;;
    *) return;;
    esac

    # don't put duplicate lines or lines starting with space in the history.
    # See bash(1) for more options
    HISTCONTROL=ignoreboth

    # append to the history file, don't overwrite it
    shopt -s histappend

    # for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
    HISTSIZE=1000
    HISTFILESIZE=2000

    # check the window size after each command and, if necessary,
    # update the values of LINES and COLUMNS.
    shopt -s checkwinsize

    # If set, the pattern "**" used in a pathname expansion context will
    # match all files and zero or more directories and subdirectories.
    #shopt -s globstar

    # make less more friendly for non-text input files, see lesspipe(1)
    [ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

    # set variable identifying the chroot you work in (used in the prompt below)
    if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)
    fi

    # set a fancy prompt (non-color, unless we know we "want" color)
    case "$TERM" in
    xterm-color|*-256color) color_prompt=yes;;
    esac

    # uncomment for a colored prompt, if the terminal has the capability; turned
    # off by default to not distract the user: the focus in a terminal window
    # should be on the output of commands, not on the prompt
    #force_color_prompt=yes

    if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
    # We have color support; assume it's compliant with Ecma-48
    # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
    # a case would tend to support setf rather than setaf.)
    color_prompt=yes
    else
    color_prompt=
    fi
    fi

    if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}[33[01;32m]u@h[33[00m]:[33[01;34m]w[33[00m]$ '
    else
    PS1='${debian_chroot:+($debian_chroot)}u@h:w$ '
    fi
    unset color_prompt force_color_prompt

    # If this is an xterm set the title to user@host:dir
    case "$TERM" in
    xterm*|rxvt*)
    PS1="[e]0;${debian_chroot:+($debian_chroot)}u@h: wa]$PS1"
    ;;
    *)
    ;;
    esac

    # enable color support of ls and also add handy aliases
    if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'
    alias fgrep='fgrep --color=auto'
    alias egrep='egrep --color=auto'
    fi

    # colored GCC warnings and errors
    #export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

    # some more ls aliases
    alias ll='ls -alF'
    alias la='ls -A'
    alias l='ls -CF'

    # Add an "alert" alias for long running commands. Use like so:
    # sleep 10; alert
    alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '''s/^s*[0-9]+s*//;s/[;&|]s*alert$//''')"'

    # Alias definitions.
    # You may want to put all your additions into a separate file like
    # ~/.bash_aliases, instead of adding them here directly.
    # See /usr/share/doc/bash-doc/examples in the bash-doc package.

    if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliases
    fi

    # enable programmable completion features (you don't need to enable
    # this, if it's already enabled in /etc/bash.bashrc and /etc/profile
    # sources /etc/bash.bashrc).
    if ! shopt -oq posix; then
    if [ -f /usr/share/bash-completion/bash_completion ]; then
    . /usr/share/bash-completion/bash_completion
    elif [ -f /etc/bash_completion ]; then
    . /etc/bash_completion
    fi
    fi

    # added by Anaconda3 installer
    export PATH="/home/kong/anaconda3/bin:$PATH"
    120,1 Bot









    share|improve this question
























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I type echo $LD_LIBRARY_PATH and got /usr/local/cuda-9.0/lib64 but when I check my bashrc file they are not there. Where are they ?



      # ~/.bashrc: executed by bash(1) for non-login shells.
      # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
      # for examples

      # If not running interactively, don't do anything
      case $- in
      *i*) ;;
      *) return;;
      esac

      # don't put duplicate lines or lines starting with space in the history.
      # See bash(1) for more options
      HISTCONTROL=ignoreboth

      # append to the history file, don't overwrite it
      shopt -s histappend

      # for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
      HISTSIZE=1000
      HISTFILESIZE=2000

      # check the window size after each command and, if necessary,
      # update the values of LINES and COLUMNS.
      shopt -s checkwinsize

      # If set, the pattern "**" used in a pathname expansion context will
      # match all files and zero or more directories and subdirectories.
      #shopt -s globstar

      # make less more friendly for non-text input files, see lesspipe(1)
      [ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

      # set variable identifying the chroot you work in (used in the prompt below)
      if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
      debian_chroot=$(cat /etc/debian_chroot)
      fi

      # set a fancy prompt (non-color, unless we know we "want" color)
      case "$TERM" in
      xterm-color|*-256color) color_prompt=yes;;
      esac

      # uncomment for a colored prompt, if the terminal has the capability; turned
      # off by default to not distract the user: the focus in a terminal window
      # should be on the output of commands, not on the prompt
      #force_color_prompt=yes

      if [ -n "$force_color_prompt" ]; then
      if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
      # We have color support; assume it's compliant with Ecma-48
      # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
      # a case would tend to support setf rather than setaf.)
      color_prompt=yes
      else
      color_prompt=
      fi
      fi

      if [ "$color_prompt" = yes ]; then
      PS1='${debian_chroot:+($debian_chroot)}[33[01;32m]u@h[33[00m]:[33[01;34m]w[33[00m]$ '
      else
      PS1='${debian_chroot:+($debian_chroot)}u@h:w$ '
      fi
      unset color_prompt force_color_prompt

      # If this is an xterm set the title to user@host:dir
      case "$TERM" in
      xterm*|rxvt*)
      PS1="[e]0;${debian_chroot:+($debian_chroot)}u@h: wa]$PS1"
      ;;
      *)
      ;;
      esac

      # enable color support of ls and also add handy aliases
      if [ -x /usr/bin/dircolors ]; then
      test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
      alias ls='ls --color=auto'
      #alias dir='dir --color=auto'
      #alias vdir='vdir --color=auto'

      alias grep='grep --color=auto'
      alias fgrep='fgrep --color=auto'
      alias egrep='egrep --color=auto'
      fi

      # colored GCC warnings and errors
      #export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

      # some more ls aliases
      alias ll='ls -alF'
      alias la='ls -A'
      alias l='ls -CF'

      # Add an "alert" alias for long running commands. Use like so:
      # sleep 10; alert
      alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '''s/^s*[0-9]+s*//;s/[;&|]s*alert$//''')"'

      # Alias definitions.
      # You may want to put all your additions into a separate file like
      # ~/.bash_aliases, instead of adding them here directly.
      # See /usr/share/doc/bash-doc/examples in the bash-doc package.

      if [ -f ~/.bash_aliases ]; then
      . ~/.bash_aliases
      fi

      # enable programmable completion features (you don't need to enable
      # this, if it's already enabled in /etc/bash.bashrc and /etc/profile
      # sources /etc/bash.bashrc).
      if ! shopt -oq posix; then
      if [ -f /usr/share/bash-completion/bash_completion ]; then
      . /usr/share/bash-completion/bash_completion
      elif [ -f /etc/bash_completion ]; then
      . /etc/bash_completion
      fi
      fi

      # added by Anaconda3 installer
      export PATH="/home/kong/anaconda3/bin:$PATH"
      120,1 Bot









      share|improve this question













      I type echo $LD_LIBRARY_PATH and got /usr/local/cuda-9.0/lib64 but when I check my bashrc file they are not there. Where are they ?



      # ~/.bashrc: executed by bash(1) for non-login shells.
      # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
      # for examples

      # If not running interactively, don't do anything
      case $- in
      *i*) ;;
      *) return;;
      esac

      # don't put duplicate lines or lines starting with space in the history.
      # See bash(1) for more options
      HISTCONTROL=ignoreboth

      # append to the history file, don't overwrite it
      shopt -s histappend

      # for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
      HISTSIZE=1000
      HISTFILESIZE=2000

      # check the window size after each command and, if necessary,
      # update the values of LINES and COLUMNS.
      shopt -s checkwinsize

      # If set, the pattern "**" used in a pathname expansion context will
      # match all files and zero or more directories and subdirectories.
      #shopt -s globstar

      # make less more friendly for non-text input files, see lesspipe(1)
      [ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

      # set variable identifying the chroot you work in (used in the prompt below)
      if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
      debian_chroot=$(cat /etc/debian_chroot)
      fi

      # set a fancy prompt (non-color, unless we know we "want" color)
      case "$TERM" in
      xterm-color|*-256color) color_prompt=yes;;
      esac

      # uncomment for a colored prompt, if the terminal has the capability; turned
      # off by default to not distract the user: the focus in a terminal window
      # should be on the output of commands, not on the prompt
      #force_color_prompt=yes

      if [ -n "$force_color_prompt" ]; then
      if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
      # We have color support; assume it's compliant with Ecma-48
      # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
      # a case would tend to support setf rather than setaf.)
      color_prompt=yes
      else
      color_prompt=
      fi
      fi

      if [ "$color_prompt" = yes ]; then
      PS1='${debian_chroot:+($debian_chroot)}[33[01;32m]u@h[33[00m]:[33[01;34m]w[33[00m]$ '
      else
      PS1='${debian_chroot:+($debian_chroot)}u@h:w$ '
      fi
      unset color_prompt force_color_prompt

      # If this is an xterm set the title to user@host:dir
      case "$TERM" in
      xterm*|rxvt*)
      PS1="[e]0;${debian_chroot:+($debian_chroot)}u@h: wa]$PS1"
      ;;
      *)
      ;;
      esac

      # enable color support of ls and also add handy aliases
      if [ -x /usr/bin/dircolors ]; then
      test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
      alias ls='ls --color=auto'
      #alias dir='dir --color=auto'
      #alias vdir='vdir --color=auto'

      alias grep='grep --color=auto'
      alias fgrep='fgrep --color=auto'
      alias egrep='egrep --color=auto'
      fi

      # colored GCC warnings and errors
      #export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

      # some more ls aliases
      alias ll='ls -alF'
      alias la='ls -A'
      alias l='ls -CF'

      # Add an "alert" alias for long running commands. Use like so:
      # sleep 10; alert
      alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '''s/^s*[0-9]+s*//;s/[;&|]s*alert$//''')"'

      # Alias definitions.
      # You may want to put all your additions into a separate file like
      # ~/.bash_aliases, instead of adding them here directly.
      # See /usr/share/doc/bash-doc/examples in the bash-doc package.

      if [ -f ~/.bash_aliases ]; then
      . ~/.bash_aliases
      fi

      # enable programmable completion features (you don't need to enable
      # this, if it's already enabled in /etc/bash.bashrc and /etc/profile
      # sources /etc/bash.bashrc).
      if ! shopt -oq posix; then
      if [ -f /usr/share/bash-completion/bash_completion ]; then
      . /usr/share/bash-completion/bash_completion
      elif [ -f /etc/bash_completion ]; then
      . /etc/bash_completion
      fi
      fi

      # added by Anaconda3 installer
      export PATH="/home/kong/anaconda3/bin:$PATH"
      120,1 Bot






      environment-variables bashrc






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 27 at 23:27









      Kong

      2841618




      2841618






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote



          accepted










          They should be in the ~/.profile file. If not, add the following to the bottom of your ~/.profile file:



          # set PATH for cuda 9.0 installation
          if [ -d "/usr/local/cuda-9.0/bin/" ]; then
          export PATH=/usr/local/cuda-9.0/bin${PATH:+:${PATH}}
          export LD_LIBRARY_PATH=/usr/local/cuda-9.0/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
          fi





          share|improve this answer





















          • thank you. i am not familiar with the syntax. does this mean LD_LIBRARY_PATH will point to multiple folders ? thats what the colon seem to suggest.
            – Kong
            Nov 27 at 23:36






          • 1




            @Kong The : are used as separators in the PATH environment. So, the above adds the /usr/local/cuda-9.0/bin folder to your PATH statement if that folder exists.
            – Terrance
            Nov 27 at 23:37






          • 1




            @Kong Oh, and the existing PATH statement should be in the /etc/environment file.
            – Terrance
            Nov 27 at 23:39










          • tyvm, i see the PATH statement. But what about the LD_LIBRARY_PATH ? I dont see it in .bashrc as well as environment
            – Kong
            Nov 27 at 23:46






          • 1




            @Kong The LD_LIBRARY_PATH should be in the same area as ~/.profile. See the second export line in my answer.
            – Terrance
            Nov 27 at 23:47











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1096643%2fwhere-is-ld-library-path-and-path%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          1
          down vote



          accepted










          They should be in the ~/.profile file. If not, add the following to the bottom of your ~/.profile file:



          # set PATH for cuda 9.0 installation
          if [ -d "/usr/local/cuda-9.0/bin/" ]; then
          export PATH=/usr/local/cuda-9.0/bin${PATH:+:${PATH}}
          export LD_LIBRARY_PATH=/usr/local/cuda-9.0/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
          fi





          share|improve this answer





















          • thank you. i am not familiar with the syntax. does this mean LD_LIBRARY_PATH will point to multiple folders ? thats what the colon seem to suggest.
            – Kong
            Nov 27 at 23:36






          • 1




            @Kong The : are used as separators in the PATH environment. So, the above adds the /usr/local/cuda-9.0/bin folder to your PATH statement if that folder exists.
            – Terrance
            Nov 27 at 23:37






          • 1




            @Kong Oh, and the existing PATH statement should be in the /etc/environment file.
            – Terrance
            Nov 27 at 23:39










          • tyvm, i see the PATH statement. But what about the LD_LIBRARY_PATH ? I dont see it in .bashrc as well as environment
            – Kong
            Nov 27 at 23:46






          • 1




            @Kong The LD_LIBRARY_PATH should be in the same area as ~/.profile. See the second export line in my answer.
            – Terrance
            Nov 27 at 23:47















          up vote
          1
          down vote



          accepted










          They should be in the ~/.profile file. If not, add the following to the bottom of your ~/.profile file:



          # set PATH for cuda 9.0 installation
          if [ -d "/usr/local/cuda-9.0/bin/" ]; then
          export PATH=/usr/local/cuda-9.0/bin${PATH:+:${PATH}}
          export LD_LIBRARY_PATH=/usr/local/cuda-9.0/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
          fi





          share|improve this answer





















          • thank you. i am not familiar with the syntax. does this mean LD_LIBRARY_PATH will point to multiple folders ? thats what the colon seem to suggest.
            – Kong
            Nov 27 at 23:36






          • 1




            @Kong The : are used as separators in the PATH environment. So, the above adds the /usr/local/cuda-9.0/bin folder to your PATH statement if that folder exists.
            – Terrance
            Nov 27 at 23:37






          • 1




            @Kong Oh, and the existing PATH statement should be in the /etc/environment file.
            – Terrance
            Nov 27 at 23:39










          • tyvm, i see the PATH statement. But what about the LD_LIBRARY_PATH ? I dont see it in .bashrc as well as environment
            – Kong
            Nov 27 at 23:46






          • 1




            @Kong The LD_LIBRARY_PATH should be in the same area as ~/.profile. See the second export line in my answer.
            – Terrance
            Nov 27 at 23:47













          up vote
          1
          down vote



          accepted







          up vote
          1
          down vote



          accepted






          They should be in the ~/.profile file. If not, add the following to the bottom of your ~/.profile file:



          # set PATH for cuda 9.0 installation
          if [ -d "/usr/local/cuda-9.0/bin/" ]; then
          export PATH=/usr/local/cuda-9.0/bin${PATH:+:${PATH}}
          export LD_LIBRARY_PATH=/usr/local/cuda-9.0/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
          fi





          share|improve this answer












          They should be in the ~/.profile file. If not, add the following to the bottom of your ~/.profile file:



          # set PATH for cuda 9.0 installation
          if [ -d "/usr/local/cuda-9.0/bin/" ]; then
          export PATH=/usr/local/cuda-9.0/bin${PATH:+:${PATH}}
          export LD_LIBRARY_PATH=/usr/local/cuda-9.0/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
          fi






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 27 at 23:33









          Terrance

          18.5k34092




          18.5k34092












          • thank you. i am not familiar with the syntax. does this mean LD_LIBRARY_PATH will point to multiple folders ? thats what the colon seem to suggest.
            – Kong
            Nov 27 at 23:36






          • 1




            @Kong The : are used as separators in the PATH environment. So, the above adds the /usr/local/cuda-9.0/bin folder to your PATH statement if that folder exists.
            – Terrance
            Nov 27 at 23:37






          • 1




            @Kong Oh, and the existing PATH statement should be in the /etc/environment file.
            – Terrance
            Nov 27 at 23:39










          • tyvm, i see the PATH statement. But what about the LD_LIBRARY_PATH ? I dont see it in .bashrc as well as environment
            – Kong
            Nov 27 at 23:46






          • 1




            @Kong The LD_LIBRARY_PATH should be in the same area as ~/.profile. See the second export line in my answer.
            – Terrance
            Nov 27 at 23:47


















          • thank you. i am not familiar with the syntax. does this mean LD_LIBRARY_PATH will point to multiple folders ? thats what the colon seem to suggest.
            – Kong
            Nov 27 at 23:36






          • 1




            @Kong The : are used as separators in the PATH environment. So, the above adds the /usr/local/cuda-9.0/bin folder to your PATH statement if that folder exists.
            – Terrance
            Nov 27 at 23:37






          • 1




            @Kong Oh, and the existing PATH statement should be in the /etc/environment file.
            – Terrance
            Nov 27 at 23:39










          • tyvm, i see the PATH statement. But what about the LD_LIBRARY_PATH ? I dont see it in .bashrc as well as environment
            – Kong
            Nov 27 at 23:46






          • 1




            @Kong The LD_LIBRARY_PATH should be in the same area as ~/.profile. See the second export line in my answer.
            – Terrance
            Nov 27 at 23:47
















          thank you. i am not familiar with the syntax. does this mean LD_LIBRARY_PATH will point to multiple folders ? thats what the colon seem to suggest.
          – Kong
          Nov 27 at 23:36




          thank you. i am not familiar with the syntax. does this mean LD_LIBRARY_PATH will point to multiple folders ? thats what the colon seem to suggest.
          – Kong
          Nov 27 at 23:36




          1




          1




          @Kong The : are used as separators in the PATH environment. So, the above adds the /usr/local/cuda-9.0/bin folder to your PATH statement if that folder exists.
          – Terrance
          Nov 27 at 23:37




          @Kong The : are used as separators in the PATH environment. So, the above adds the /usr/local/cuda-9.0/bin folder to your PATH statement if that folder exists.
          – Terrance
          Nov 27 at 23:37




          1




          1




          @Kong Oh, and the existing PATH statement should be in the /etc/environment file.
          – Terrance
          Nov 27 at 23:39




          @Kong Oh, and the existing PATH statement should be in the /etc/environment file.
          – Terrance
          Nov 27 at 23:39












          tyvm, i see the PATH statement. But what about the LD_LIBRARY_PATH ? I dont see it in .bashrc as well as environment
          – Kong
          Nov 27 at 23:46




          tyvm, i see the PATH statement. But what about the LD_LIBRARY_PATH ? I dont see it in .bashrc as well as environment
          – Kong
          Nov 27 at 23:46




          1




          1




          @Kong The LD_LIBRARY_PATH should be in the same area as ~/.profile. See the second export line in my answer.
          – Terrance
          Nov 27 at 23:47




          @Kong The LD_LIBRARY_PATH should be in the same area as ~/.profile. See the second export line in my answer.
          – Terrance
          Nov 27 at 23:47


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1096643%2fwhere-is-ld-library-path-and-path%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Quarter-circle Tiles

          build a pushdown automaton that recognizes the reverse language of a given pushdown automaton?

          Mont Emei