environment variables $MKLROOT, $INCLUDE, and $LIBRARY_PATH

Asked by Stojan Kitanov

Hi Jan,

I have question about the environment variables.

When I open terminal I get this:

bash: /opt/intel/composer_xe_2011_sp1.7.256/mkl/bin/mklvars.sh: No such file or directory
stojan@stojan-K52JT:~$ echo $MKLROOT

stojan@stojan-K52JT:~$

As you can see when I type echo $MKLROOT I don't get any output.

I added . /opt/intel/mkl/bin/mklvars.sh intel64
at the bottom of bashrc file

stojan@stojan-K52JT:~$ gedit ~/.bashrc

# ~/.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
[ -z "$PS1" ] && return

# 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) 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)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[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: \w\a\]$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

# 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 [ -f /etc/bash_completion ] && ! shopt -oq posix; then
    . /etc/bash_completion
fi

. /opt/intel/composer_xe_2011_sp1.7.256/mkl/bin/mklvars.sh intel64

Is it correct like this or I am doing something wrong.

Regards,

Stojan

Question information

Language:
English Edit question
Status:
Solved
For:
IMTAphy Edit question
Assignee:
No assignee Edit question
Solved by:
Stojan Kitanov
Solved:
Last query:
Last reply:
Revision history for this message
Jan (jan-ellenbeck) said :
#1

Hi,

it looks good but I can't know if your path is correct...

You don't seem to have this file:
/opt/intel/composer_xe_2011_sp1.7.256/mkl/bin/mklvars.sh

Did you install Intel MKL on that machine? Did install it into that directory?

Cheers
Jan

Revision history for this message
Maciej Muehleisen (mue-comnets) said :
#2

Hi,

the line should be

source /opt/intel/composer_xe_2011_sp1.7.256/mkl/bin/mklvars.sh intel64

the dot at the beginning leads to a wrong path. For me even

source /opt/intel/mkl/bin/mklvars.sh intel64

works and I guess it should also work for you if all symbolic links have been created right at MKL installation.

Greats,

Mac

Revision history for this message
Stojan Kitanov (stojankitanov) said :
#3

Ok I solved it now and it is ok.

I opened terminal and I typed this command.

. /opt/intel/mkl/bin/mklvars.sh intel64

I got this output:

/opt/intel/composer_xe_2011_sp1.10.319/mkl

So I add the output in the bashrc file, i.e.

. /opt/intel/composer_xe_2011_sp1.10.319/mkl

And now it is ok.

Thanks for your help again.

Now I will start to do some simulations.

Any sugestions from where to start, because I am very new beginner.

Regards,

Stojan

Revision history for this message
Stojan Kitanov (stojankitanov) said :
#4

Sorry I add this line in bashrc:

. /opt/intel/composer_xe_2011_sp1.10.319/mkl/bin/mklvars.sh intel64

I typed wrong in the comment.

Regards,

Stojan