undefined reference to `for_ifcore_version'

[Mohammed_A_5]

Hi
I wanted to compile a code with MPICH 3.1 but I get the error:

/opt/intel/compilers_and_libraries_2016.0.109/linux/compiler/lib/intel64/libifport.so.5: undefined reference to `for_ifcore_version'

I have the Intel Parallel Studio XE Composer Edition for Fortran and C++ (Linux) (parallel_studio_xe_2016.0.047) installed.

and the .bashrc has the environment variables:

source /opt/intel/compilers_and_libraries/linux/bin/compilervars.sh -arch intel64 -platform linux

LD_LIBRARY_PATH="/home/mohammed/mpich3/bin:$LD_LIBRARY_PATH"
export LD_LIBRARY_PATH

and when I test the ifort and MPI I got :

:~$ which ifort
/opt/intel/compilers_and_libraries_2016.0.109/linux/bin/intel64/ifort
:~$ ifort -v
ifort version 16.0.0
:~$ which mpicc
/home/mohammed/mpich3/bin/mpicc
:~$ which mpiexec
/opt/intel/compilers_and_libraries_2016.0.109/linux/mpi/intel64/bin/mpiexec
any suggestions

thanks

[Mohammed_A_5]

Kevin Davis (Intel) wrote:

Ok, thank you. The key environment variable settings include paths to both the 2015 and 2016 products on your system. As a first step, we need to setup your environment to use the 2016 product exclusively. Going back to your original post, you indicate having the compilervars.sh in your .bashrc.

Given that, please start a new login session and check the PATH variable using the command: echo $PATH

You do not want to see any reference to 2015.1.133 in the output of that command.

If you do then you have to track down where on your system something is sourcing the 2015 setup script. I could be compilervars.sh or ifortvars.sh and referenced from /opt/intel/composer_xe_2015/bin. If it happens after you login then its happening as part of the login process so you might look at your .bashrc and .bash_profile perhaps.

If there is no evidence of 2015.1.133, then follow your other steps to setup your environment you indicated were needed to use your MPICH 3.1. After that setup is complete, remove the -watch option we added to the makefile, do a clean (‘make clean’ - or whatever this app requires), then run the make. Hopefully the build will succeed.

Hi Kevin

this what I got from echo commandc

/opt/intel/compilers_and_libraries_2016.0.109/linux/bin/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/mpi/intel64/bin:/opt/intel/debugger_2016/gdb/intel64_mic/bin:/opt/intel/compilers_and_libraries_2016.0.109/linux/bin/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/mpi/intel64/bin:/opt/intel/debugger_2016/gdb/intel64_mic/bin:/opt/intel/composer_xe_2015.1.133/bin/intel64:/opt/intel/composer_xe_2015.1.133/debugger/gdb/intel64_mic/bin:/home/mohammed/tec/bin:/home/mohammed/mpich3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games

I traced the /opt/intel/composer_xe_2015.1.133/bin/intel64 and change it in my profile.d but the problem still same
regards

[Kevin_D_Intel]

That's fine. Let me make sure I understand clearly before we move on.

What did you have to change in your profile?   Was it source-ing the compilervars.sh from the 2015 release?

After you changed your profile, did you open a new terminal and echo the $PATH, confirm there was no 2015.1.133 reference, then run make and the same link error appeared?

[Mohammed_A_5]

Kevin Davis (Intel) wrote:

That's fine. Let me make sure I understand clearly before we move on.

What did you have to change in your profile?   Was it source-ing the compilervars.sh from the 2015 release?

After you changed your profile, did you open a new terminal and echo the $PATH, confirm there was no 2015.1.133 reference, then run make and the same link error appeared?

HI

yes it was compilervars.sh yhat refers to 2015.1.133 and I replaced it with one that refers to 2016. Then I restarted my machine and run echo command and send the output. 

By the way, my machine is Linux Ubuntu 14.04LTS Does this make any diference?

Regards

[Kevin_D_Intel]

The brand/version of the OS is not a factor. This is something related to the setup on the system itself. If I follow what you said, it sounds like someone has changed the global shell start up scripts to perhaps source the compilervars for all users when their shell starts up.

Do you have a system administrator for your system?

Do you see any reference to the 2015 compilervars in either of these files on your system:

/etc/.profile
/etc/bash.bashrc

[Mohammed_A_5]

Kevin Davis (Intel) wrote:

The brand/version of the OS is not a factor. This is something related to the setup on the system itself. If I follow what you said, it sounds like someone has changed the global shell start up scripts to perhaps source the compilervars for all users when their shell starts up.

Do you have a system administrator for your system?

Do you see any reference to the 2015 compilervars in either of these files on your system:

/etc/.profile
/etc/bash.bashrc

Hi kevin

Yes I'm the administrator of the system and I found refrence to the 2015 in bash.bashrc. I change it and the echo $PATH gave me this :

echo $PATH
/opt/intel/compilers_and_libraries_2016.0.109/linux/bin/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/mpi/intel64/bin:/opt/intel/debugger_2016/gdb/intel64_mic/bin:/opt/intel/compilers_and_libraries_2016.0.109/linux/bin/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/mpi/intel64/bin:/opt/intel/debugger_2016/gdb/intel64_mic/bin:/opt/intel/compilers_and_libraries_2016.0.109/linux/bin/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/mpi/intel64/bin:/opt/intel/debugger_2016/gdb/intel64_mic/bin:/home/mohammed/tec/bin:/home/mohammed/mpich3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games.

but I still have the same message when I try to compile my code

Regards

Mohammed

[Kevin_D_Intel]

That's fine. I was somewhat expecting that. I just wanted to take one step at a time to eliminate possible causes.

Now let's move on to your MPICH 3.1 in your home area that you are using. Since you are the admin, I assume you ran the configure step for the MPICH 3.1 build you are using from your home area.

A few questions:

- Do you recall whether your environment was setup for the 2015 or 2016 Intel compiler release when you ran configure?
- Did you follow their prescribed command-lines from their mpich-3.1.3-README.txt that use the tee command?
- If you so, assuming you still have them, can you search the c.txt, m.txt, mi.txt files for any evidence of the Intel 2015 release that we have been discussing?

Perhaps you could try some searches for the string 2015.1.133, or ifort, or 2015.

I'm looking for any evidence your environment might have been  pre-initialized for the 2015.1.133 release when the MPICH 3.1 was configured. If that were the case, I expect it would explain why the build is still failing.

Another option, and maybe something I recommend you consider, is now that we have your environment setup for the 2016 release exclusively, you could opt to discard the current MPICH 3.1 and redo the steps to configure, build, and install. That might save a lot of time.

[Mohammed_A_5]

Kevin Davis (Intel) wrote:

That's fine. I was somewhat expecting that. I just wanted to take one step at a time to eliminate possible causes.

Now let's move on to your MPICH 3.1 in your home area that you are using. Since you are the admin, I assume you ran the configure step for the MPICH 3.1 build you are using from your home area.

A few questions:

- Do you recall whether your environment was setup for the 2015 or 2016 Intel compiler release when you ran configure?
- Did you follow their prescribed command-lines from their mpich-3.1.3-README.txt that use the tee command?
- If you so, assuming you still have them, can you search the c.txt, m.txt, mi.txt files for any evidence of the Intel 2015 release that we have been discussing?

Perhaps you could try some searches for the string 2015.1.133, or ifort, or 2015.

I'm looking for any evidence your environment might have been  pre-initialized for the 2015.1.133 release when the MPICH 3.1 was configured. If that were the case, I expect it would explain why the build is still failing.

Another option, and maybe something I recommend you consider, is now that we have your environment setup for the 2016 release exclusively, you could opt to discard the current MPICH 3.1 and redo the steps to configure, build, and install. That might save a lot of time.

Thank you very much

I took the option 2 and re-installed the MPICH and it went ok.

Regards

Mohammed

[Kevin_D_Intel]

You're welcome. Glad we resolved this.