Error:#11025 and #10014 in linux

[Lee_A_]

My system is fedora 19 , the version is :

Linux version 3.14.27-100.fc19.x86_64 (mockbuild@bkernel02.phx2.fedoraproject.org) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-7) (GCC) ) #1 SMP Wed Dec 17 19:36:34 UTC 2014

The ifort is parallel_studio_xe2016 for students, when inpit ''ifort --version'' in the terminal,there is :

ifort (IFORT) 16.0.0 20150815
Copyright (C) 1985-2015 Intel Corporation.  All rights reserved.

When compile a file with 'ifort 't.f95'(could be compiled with g95),there is :

ipo: error #11025: Linker command line is badly formed
ifort: error #10014: problem during multi-file optimization compilation (code 1)

If input 'ifot',there is :

ifort: command line error: no files specified; for help type "ifort -help"

Then I try to use 't.f90',input 'ifort t.f90 -o a.e',there is :

fortcom: Severe: No such file or directory

... file is 'daalvars.csh*'
compilation aborted for t.f90 (code 1).

That's all information I get.

Thank you for your help!

[mecej4]

Kevin, here is an improbable explanation.

If the user modified, per instructions to do so, a shell script in a screen-editor such as vi, entered Insert mode, pressed cursor-positioning keys (arrow keys) in that mode and then pressed Esc, fragments of escape sequences would be present in the modified shell script. Such occurrences used to be a problem in the old days when we used serial communications between terminals and computers over noisy lines.

Does the user have the original script (ifortvars.sh, etc.) as distributed, or does it have a different file-size, check-sum, etc.?

[Kevin_D_Intel]

Although maybe not. The daalvars.sh, as it turns out, is the only script that builds its path based on the ${BASH_SOURCE[0]}.

What if such editing actions you describe occurred while inserting a 'source' command into one's .bashrc (or similar)?  Just maybe those fragments or escape sequences appeared at the beginning of the string /opt/intel/compilers_and_libraries_2016.0.109/linux/bin/compilervars.sh. Those could perhaps be replicated in ${BASH_SOURCE[0]}, and make their way into the daal path component. I was not able to synthesize anything like that so we'll see what Lee A. has to say.

[Lee_A_]

Kevin Davis (Intel) wrote:

Thank you for all the details. Those are helping understand where the original compiler error has come from. From what I see, the whole set of important environment variables (LD_LIBRARY_PATH, PATH, etc.) are corrupted with a malformed DAAL related path. For reasons I don’t yet know, it appears the underlying daalvars.sh (called automatically by source’ing compilervars.sh) malfunctioned on your system leading to a malformed daal path that was then incorporated into these important environment variables.

Here is what I’d like you to do as a work around. Copy the file /opt/intel/compilers_and_libraries_2016.0.109/linux/bin/compilervars.sh to your home directory. Open this copy in your home area with your preferred editor. Next, for lines 106-108 as shown below, delete them from your file.

106     if [ -e $PROD_DIR/daal/bin/daalvars.sh ]; then
107          . $PROD_DIR/daal/bin/daalvars.sh $TARGET_ARCH
108     fi

Next, save these changes and exit the editor. Next, from a fresh login window on your system, from your home directory run the command: source ./compilervars.sh intel64

Next, try the compilation as we have asked before using your t.95 source file (e.g. ifort -free -Tf t.f95)

If that works then you will finally be able to move forward.  Then, just for now, when you login and want to use the compiler you can use your local copy of compilervars.sh. If you have root access and you feel comfortable making a change to the script in the /opt/intel area, then you could edit it and insert a comment character # at the beginning of lines 106-108. That edit could then be undone once we understand the root cause of the malformed daal path.

Once I get you moving forward I'll come back and ask if we can conduct some other tests on your system if needed to understand the daalvars.sh malfunction.

Keep me posted!

After note the lines 106-108 in 'compilervars.sh' with #,  ifort is working.

Thanks for you patience on my question very much! Now my error has solved!

[Kevin_D_Intel]

I am glad to hear that. The issue is not completely solved but at least you can move forward with your interest for now. I still need to try to understand how the bad path came to be.

Just a few other questions for now:

Did you make a private copy of compilervars.sh and edit to add '#' on those lines, or did you edit the original copy under /opt/intel/compilers_and_libraries_2016.0.109/linux/bin/compilervars.sh to add '#', or did you maybe do both?

When you are using the source command with the compilervars.sh script, are you entering the complete command at your shell prompt or have you added the source command to any of your .bashrc (or similar) files?

Could you look in your home directory for the "dot" history (i.e. .history) hidden file and upload that in your reply?

Thank you

[Lee_A_]

Kevin Davis (Intel) wrote:

I am glad to hear that. The issue is not completely solved but at least you can move forward with your interest for now. I still need to try to understand how the bad path came to be.

Just a few other questions for now:

Did you make a private copy of compilervars.sh and edit to add '#' on those lines, or did you edit the original copy under /opt/intel/compilers_and_libraries_2016.0.109/linux/bin/compilervars.sh to add '#', or did you maybe do both?

When you are using the source command with the compilervars.sh script, are you entering the complete command at your shell prompt or have you added the source command to any of your .bashrc (or similar) files?

Could you look in your home directory for the "dot" history (i.e. .history) hidden file and upload that in your reply?

Thank you

I edit the original file 'compilervars.sh' in root under /opt/intel/compilers_and_libraries_2016.0.109/linux/bin/compilervars.sh adding '#'

I add the command

'source /opt/intel/compilers_and_libraries_2016.0.109/linux/bin/compilervars.sh' 

in my .bashrc  file.

I'm sorry I removed my file .bash_history.....  Instead of a .history file,perhaps I can attach my  .bashrc?477923

[Kevin_D_Intel]

Yes, sorry, I meant .bash_history.

One thing I see in your .bashrc is an unnecessary source of the ifortvars.sh. You only need to source the compilervars.sh so remove the line with ifortvars.sh.

Next, I somewhat suspect a scenario occurred like mecej4 noted. When it is convenient for you, it would be nice to have you remove the '#' from the /opt/intel/compilers_and_libraries_2016.0.109/linux/bin/compilervars.sh file, and then open a new terminal session to your system and use the env command to look at the variables like CPATH, LD_LIBRARY_PATH, etc. to see whether there are malformed paths related to the daalvars.csh as shown below:

LD_LIBRARY_PATH=/opt/intel/compilers_and_libraries_2016.0.109/linux/compiler/lib/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/mpi/intel64/lib:/opt/intel/compilers_and_libraries_2016.0.109/linux/ipp/../compiler/lib/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/ipp/lib/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/compiler/lib/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/mkl/lib/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/tbb/lib/intel64/gcc4.1:/opt/intel/debugger_2016/libipt/intel64/lib:/opt/intel/compilers_and_libraries_2016.0.109/linux/daal
daalvars.csh*
daalvars.sh*
/opt/intel/compilers_and_libraries_2016.0.109/linux/daal/bin/lib/intel64_lin:/opt/intel/compilers_and_libraries_2016.0.109/linux/daal

You can also try the compile command we have been using with your t.95 source file.

It is very possible the error you experienced initially was something that came about by accident and is unlikely to happen again.

[Lee_A_]

Kevin Davis (Intel) wrote:

Yes, sorry, I meant .bash_history.

One thing I see in your .bashrc is an unnecessary source of the ifortvars.sh. You only need to source the compilervars.sh so remove the line with ifortvars.sh.

Next, I somewhat suspect a scenario occurred like mecej4 noted. When it is convenient for you, it would be nice to have you remove the '#' from the /opt/intel/compilers_and_libraries_2016.0.109/linux/bin/compilervars.sh file, and then open a new terminal session to your system and use the env command to look at the variables like CPATH, LD_LIBRARY_PATH, etc. to see whether there are malformed paths related to the daalvars.csh as shown below:

LD_LIBRARY_PATH=/opt/intel/compilers_and_libraries_2016.0.109/linux/compiler/lib/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/mpi/intel64/lib:/opt/intel/compilers_and_libraries_2016.0.109/linux/ipp/../compiler/lib/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/ipp/lib/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/compiler/lib/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/mkl/lib/intel64:/opt/intel/compilers_and_libraries_2016.0.109/linux/tbb/lib/intel64/gcc4.1:/opt/intel/debugger_2016/libipt/intel64/lib:[3;J[H[2J/opt/intel/compilers_and_libraries_2016.0.109/linux/daal
[0m[38;5;40mdaalvars.csh[0m*
[38;5;40mdaalvars.sh[0m*
/opt/intel/compilers_and_libraries_2016.0.109/linux/daal/bin/lib/intel64_lin:[3;J[H[2J/opt/intel/compilers_and_libraries_2016.0.109/linux/daal

You can also try the compile command we have been using with your t.95 source file.

It is very possible the error you experienced initially was something that came about by accident and is unlikely to happen again.

Actually I source only ifortvars.sh at the beginning for I just need fortran (I use ifort for  academic and I get a student-free version with my  e-mail 'edu.cn' from the intel website).

I attach my output after env as the file 'env.txt' here(I cannot find 'daalcars' in the output.....).

477936

PS.The error occured as soon as I remove '#' from the compilervars.sh file.

[Kevin_D_Intel]

ifortvars.sh is a symbolic-link to compilervars.sh so using either name does the same thing, but you only need to use one of them and not both one after the other like what I saw in your earlier .bashrc. If you only have ifortvars.sh in your .bashrc, now then that is fine.

Yes, the env.txt looks great. The paths for daal are correct, but your PS has me confused.

Can you explain that comment a bit further?
Are you saying when you use ifortvars.sh there is no problem and when you use compilervars.sh there is?

[Lee_A_]

Kevin Davis (Intel) wrote:

ifortvars.sh is a symbolic-link to compilervars.sh so using either name does the same thing, but you only need to use one of them and not both one after the other like what I saw in your earlier .bashrc. If you only have ifortvars.sh in your .bashrc, now then that is fine.

Yes, the env.txt looks great. The paths for daal are correct, but your PS has me confused.

Can you explain that comment a bit further?
Are you saying when you use ifortvars.sh there is no problem and when you use compilervars.sh there is?

Sorry for my expression.I mean that if I removed '#' from compilervars.sh ,the error in compilation occured again,no matter I source ifortvars.sh  or compilervars.sh