Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Compilation Error (Fortran)

Anatoly_Perov
Beginner
9,294 Views
Hello, colleagues!
Please, help me to solve the following problem which arises during my project compilation. The project is made using MS Visual Studio 2008 Professional Edition, compilation is carried out with the help of Intel Visual Fortran 11.1.067 compiler.
During the project compilation I get the message:
***************************************************************************************

1>------ : : QWin1, : Debug Win32 ------

1>Compiling with Intel Visual Fortran 11.1.067 [IA-32]...

1>Program.f90

1>Intel Fortran Compiler for applications running on IA-32, Version 11.1 Build 20100806 Package ID: w_cprof_p_11.1.067

1>Copyright (C) 1985-2010 Intel Corporation. All rights reserved.

1>catastrophic error: Compiler configuration problem encountered. The expected target architecture compiler is missing (unset != 11.1-ia32)

1>compilation aborted for D:\\ \\VStudio\\QWin1\\QWin1\\Program.f90 (code 1)

1>

1>Build log written to "file://D:\\ \\VStudio\\QWin1\\QWin1\\Debug\\BuildLog.htm"

1>QWin1 - 1 error(s), 0 warning(s)

========== : : 0, : 1, : 0, : 0 ==========

****************************************************************************************
OR using x64 platform:
***************************************************************************************

1>------ : : QWin1, : Debug x64 ------

1>Compiling with Intel Visual Fortran 11.1.067 [Intel 64]...

1>Program.f90

1>Intel Fortran Compiler for applications running on Intel 64, Version 11.1 Build 20100806 Package ID: w_cprof_p_11.1.067

1>Copyright (C) 1985-2010 Intel Corporation. All rights reserved.

1>catastrophic error: Compiler configuration problem encountered. The expected target architecture compiler is missing (unset != 11.1-intel64)

1>compilation aborted for D:\\ \\VStudio\\QWin1\\QWin1\\Program.f90 (code 1)

1>

1>Build log written to "file://D:\\ \\VStudio\\QWin1\\QWin1\\x64\\Debug\\BuildLog.htm"

1>QWin1 - 1 error(s), 0 warning(s)

========== : : 0, : 1, : 0, : 0 ==========


***************************************************************************************

Please, help me to solve the problem. I use OS Windows 7, Intel Core i7 870 processor.
0 Kudos
1 Solution
Steven_L_Intel1
Employee
9,294 Views
Tim's comments regarding PATH are not relevant to your problem. Would you please attach the buildlog.htm file from the Debug subfolder of your project? Also, please try creating a project in a path that does not contain Cyrilic characters.

View solution in original post

0 Kudos
13 Replies
TimP
Honored Contributor III
9,294 Views
Are you compiling in the Fortran Build Environment for which the shortcut should be present on the Start menu? It looks like you don't have consistent PATH settings.
0 Kudos
Steven_L_Intel1
Employee
9,294 Views
This is a Visual Studio build. I've never seen that particular error before but would suggest uninstalling and reinstalling the compiler.
0 Kudos
Anatoly_Perov
Beginner
9,294 Views
Thank you. Yes, I have the shortcut on the Start menu. I can do many things but, unfortunatelly, I am not a deep programmer. Sorry, TimP(Intel), but I do not understand what I must do with PATH settings. During compiler installation the system informed me that it will modify the PATH. I hope that you understand me and my difficulties...
0 Kudos
Anatoly_Perov
Beginner
9,294 Views
Yes, Steve... I did it three or four times before I wrote to the Forum. But it didn't solve the problem. I'm a physicist, not a system programmer. So, it is very difficult for me to understand what I must do when my computer send me such error messages. I have never seen that error before, too. Thank you, Steve, for participation. I should think about my problem decision again and I should be very obliged you and your colleagues for any idea.
0 Kudos
Steven_L_Intel1
Employee
9,295 Views
Tim's comments regarding PATH are not relevant to your problem. Would you please attach the buildlog.htm file from the Debug subfolder of your project? Also, please try creating a project in a path that does not contain Cyrilic characters.
0 Kudos
Anatoly_Perov
Beginner
9,294 Views
Hello, Steve!
You can find the Buildlog.htm files below

Best regards, Anatoly
*****************************************

Build Log

Build started: Project: QWin1, Configuration: Debug|x64

Output

Deleting intermediate files and output files for project 'QWin1', configuration 'Debug|x64'.

Compiling with Intel Visual Fortran 11.1.067 [Intel 64]...

ifort /nologo /debug:full /gen-interfaces /warn:interfaces /module:"x64\Debug\" /object:"x64\Debug\" /traceback /check:bounds /libs:qwin /dbglibs /c /Qvc9 /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\amd64" "D:\MyFolder\VStudio\QWin1\QWin1\Program.f90"

Intel Fortran Compiler for applications running on Intel 64, Version 11.1 Build 20100806 Package ID: w_cprof_p_11.1.067

Copyright (C) 1985-2010 Intel Corporation. All rights reserved.

catastrophic error: Compiler configuration problem encountered. The expected target architecture compiler is missing (unset != 11.1-intel64)

compilation aborted for D:\MyFolder\VStudio\QWin1\QWin1\Program.f90 (code 1)

QWin1 - 1 error(s), 0 warning(s)

**************************************************************

Build Log

Build started: Project: QWin1, Configuration: Debug|Win32

Output

Deleting intermediate files and output files for project 'QWin1', configuration 'Debug|Win32'.
Compiling with Intel Visual Fortran 11.1.067 [IA-32]...
ifort /nologo /debug:full /Od /QxHost /gen-interfaces /warn:interfaces /module:"Debug\" /object:"Debug\" /traceback /check:bounds /libs:qwin /dbglibs /c /Qvc9 /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin" "D:\MyFolder\VStudio\QWin1\QWin1\Program.f90"
Intel Fortran Compiler for applications running on IA-32, Version 11.1 Build 20100806 Package ID: w_cprof_p_11.1.067
Copyright (C) 1985-2010 Intel Corporation. All rights reserved.
catastrophic error: Compiler configuration problem encountered. The expected target architecture compiler is missing (unset != 11.1-ia32)
compilation aborted for D:\MyFolder\VStudio\QWin1\QWin1\Program.f90 (code 1)

QWin1 - 1 error(s), 0 warning(s)

*****************************************
0 Kudos
mecej4
Honored Contributor III
9,294 Views
Are you running a 64-bit version of Windows-7, or a 32-bit version?

The error messages from the compiler suggest one or more of the following problems with your setup:

i) your build process is calling fortcom.exe directly instead of through ifort.exe.

See http://software.intel.com/en-us/forums/showthread.php?t=75898 .

ii) there is a problem with your setup, as indicated by the presence of the symbol value "unset" in "unset != 11.1-intel64". With the proper setup, the value should be either "11.1-ia32" or "11.1-intel64", not "unset".

See http://origin-software.intel.com/en-us/forums/showthread.php?t=75377 .

Perhaps one of the Intel personnel can use this observation to identify the problem with your setup.
0 Kudos
Steven_L_Intel1
Employee
9,294 Views
Anatoly is doing the build from Visual Studio, and the log shows that ifort, not fortcom, is being invoked. The user is not the one who sets the "target architecture" in this case - it is done by ifort.

Please try this to help me further understand the problem. In the properties for the project, go to Fortran > Command Line. Add this to "Additional options"

/#x

Now do a build and show me the output.
0 Kudos
Anatoly_Perov
Beginner
9,294 Views
Steve, I did it. The Buildlog.htm is below.

Build Log

Build started: Project: QWin1, Configuration: Debug|Win32

Output

Deleting intermediate files and output files for project 'QWin1', configuration 'Debug|Win32'.

Compiling with Intel Visual Fortran 11.1.067 [IA-32]...

ifort /nologo /debug:full /Od /QxHost /gen-interfaces /warn:interfaces /module:"Debug\" /object:"Debug\" /traceback /check:bounds /libs:qwin /dbglibs /c /#x /Qvc9 /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin" "D:\MyFolder\VStudio\QWin1\QWin1\Program.f90"

C:\PROGRA~2\Intel\Compiler\11.1\067\bin\ia32\fortcom \

-D__INTEL_COMPILER=1110 \

-D_DEBUG \

-D_MT \

-D_M_IX86=700 \

-D_WIN32 \

-D__INTEL_COMPILER_BUILD_DATE=20100806 \

-mGLOB_pack_sort_init_list \

"-ID:\MyFolder\VStudio\QWin1\QWin1" \

-I. \

-IC:\PROGRA~2\Intel\Compiler\11.1\067\include\ia32 \

"-IC:\Program Files (x86)\Intel\Compiler\11.1\067\include" \

"-IC:\Program Files (x86)\Intel\Compiler\11.1\067\include\ia32" \

"-IC:\Program Files (x86)\Intel\Compiler\11.1\067\mkl\include" \

"-IC:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\atlmfc\include" \

"-IC:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\include" \

"-IC:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\PlatformSDK\include" \

"-IC:\Program Files\Microsoft SDKs\Windows\v6.0A\include" \

"-check bounds" \

"-fp_modbits honor_f32_conversion" \

-gen_interfaces \

"-module Debug" \

-O0 \

-g2 \

"-reentrancy threaded" \

-traceback \

"-warn interfaces" \

-mP1OPT_version=11.1-ia32 \

-mGLOB_diag_file=Debug\Program.diag \

-mGLOB_source_language=GLOB_SOURCE_LANGUAGE_F90 \

-mGLOB_tune_for_fort \

-mGLOB_use_fort_dope_vector \

-mP2OPT_static_promotion \

-mP1OPT_print_version=FALSE \

-mP3OPT_use_mspp_call_convention \

"-mGLOB_options_string=-nologo -debug:full -Od -QxHost -gen-interfaces -warn:interfaces -module:Debug\ -object:Debug\ -traceback -check:bounds -libs:qwin -dbglibs -c -#x -Qvc9 -Qlocation,link,C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin" \

-mGLOB_cxx_limited_range=FALSE \

-mGLOB_traceback \

-mP3OPT_defaultlibs_omit=FALSE \

-mP3OPT_defaultlibs=P3OPT_DEFAULTLIBS_STATIC_MULTITHREAD_DEBUG \

-mP3OPT_defaultlibs_select=P3OPT_DEFAULTLIBS_SELECT_F90_IVF \

-mP3OPT_defaultlibs_f90_port \

-mP3OPT_defaultlibs_f90_quickwin \

-mP1OPT_check_stack \

-mP3OPT_emit_line_numbers \

-mP2OPT_suppress_unreferenced_locals=FALSE \

-mGLOB_debug_format=GLOB_DEBUG_FORMAT_CV8 \

-mGLOB_machine_model=GLOB_MACHINE_MODEL_PW \

-mGLOB_maintain_errno \

-mGLOB_noinline_intrinsics \

-mGLOB_use_base_pointer \

-mGLOB_extended_instructions=0x400 \

-mGLOB_advanced_optim=TRUE \

-mP2OPT_hlo_check_bounds \

-mP2OPT_subs_out_of_bound=FALSE \

-mGLOB_ansi_alias \

-mIPOPT_ninl_limit=0 \

-mIPOPT_ninl_user_level=0 \

-mP2OPT_align_array_to_cache_line=FALSE \

-mGLOB_opt_level=0 \

-mIPOPT_obj_output_file_name=Debug\Program.obj \

-mGLOB_os_target=GLOB_OS_TARGET_WINNT \

-mP3OPT_asm_target=P3OPT_ASM_TARGET_MASM5 \

-mP3OPT_obj_target=P3OPT_OBJ_TARGET_NTCOFF \

-mP3OPT_enable_safeseh=TRUE \

-mGLOB_obj_output_file=Debug\Program.obj \

-mGLOB_source_dialect=GLOB_SOURCE_DIALECT_FORTRAN \

"-mP1OPT_source_file_name=D:\MyFolder\VStudio\QWin1\QWin1\Program.f90" \

"D:\MyFolder\VStudio\QWin1\QWin1\Program.f90"

Intel Fortran Compiler for applications running on IA-32, Version 11.1 Build 20100806 Package ID: w_cprof_p_11.1.067

Copyright (C) 1985-2010 Intel Corporation. All rights reserved.

catastrophic error: Compiler configuration problem encountered. The expected target architecture compiler is missing (unset != 11.1-ia32)

compilation aborted for D:\MyFolder\VStudio\QWin1\QWin1\Program.f90 (code 1)

del C:\Users\50EB~1\AppData\Local\Temp\39362arg

QWin1 - 1 error(s), 0 warning(s)

0 Kudos
Lorri_M_Intel
Employee
9,294 Views
Hi --

I think the problem comes because fortcom.exe (the actual compiler executable) cannot open the .arg file created by ifort.exe (the compiler driver, which invokes the compiler executable, and optionally other tools such as the preprocessor)

Now, of course, we need to resolve *why* fortcom can't open the intermediatefile.

There are two things that come to my mind; either the file is in UTF-8 and fortcom can't open it, or the path is in UTF-8 andfortcom can't"find" it.

Would you try one thing please? Replace the/#x thatSteve recommended a few posts ago, with /Q_keep.That switch is another undocumented internal switchthat puts the intermediate .arg file in the current working directory rather than TEMP, and does not delete the file.

After your build, you should find "fortcom.arg",containinginformationmuch like what you displayed in the build output.

If the compilation succeeded, thenthe problem was TEMP had characters thatcaused fortcom to fail.

If the compilation did not succeed, we can take a closer look at the fortcom.arg file. One option would be to submit it to Premier (just thefortcom.arg file; Iwouldn't want/need youractual source files) so we could look closer.



- Lorri

0 Kudos
Steven_L_Intel1
Employee
9,294 Views
You can also attach the fortcom.arg to a reply here and I'll get it to Lorri.
0 Kudos
Anatoly_Perov
Beginner
9,294 Views
So, the process of project compiling took place successfully! No problem. The reason was that the name of one of the folders that contained the project files has been written in Russian.

Steve, you were absolutelly right when wrote me "Also, please try creating a project in a path that does not contain Cyrilic characters." I checked the folder names again and found some cyrilic characters.
Now I know very important RULE: NEVER USE THE NATIONAL ALPHABET CHARACTERS IN FILE NAMES!!!!!!!!! EVEN YOUR SYSTEM SUPPORTS IT. This is A CATASTROPHIC ERROR.

Thank you very much, Steve!

Thank you all for your participation.
Regards, Anatoly A. Perov
0 Kudos
Steven_L_Intel1
Employee
9,294 Views
Anatoly,

I am glad to hear that you got it working. However, I think that it SHOULD have worked with Cyrilic characters in the path. I will ask our developers to look at this.
0 Kudos
Reply