Warning : platform 'Itanium' not present

[rase]

When I start a large mixed language solution I always receive a warning "platform 'Itanium' not present" from the two C/C++ projects in the solution. I was not able to find any reference to the Itanium processor in the project properties, nor a possiblity to get rid of the warning message. The warning seems not to have any further impact, but I would like to know more about the reason for the message.

Environment: Windows 7 64 bit, VS 2012, Composer 2015 

[IanH]

Is an IA64 platform (versus x64) configuration defined for any project in the solution?

[rase]

I never intented to use an Itanium processor for the solution. I don't know how to set the IA64 option for Fortran or C/C++ projects. But my experience tells me not to trust myself too much. I might have set the IA64 option by chance sometimes long ago, but I was not able to find a trace of it in the properties. I would like to get rid of the warning message to avoid unknown consequences in the future.

[TimP]

If you have object files which aren't rebuilt automatically with x64 (amd64) machine tag you should examine for any ia64 tag.

[Steven_L_Intel1]

Select Build > Configuration Manager. You have one or more projects set to IA64 as the platform.

[rase]

Sorry, Lionel, there is no reference to IA64 in any project in that solution, only to Win32 and x64, at least following what I was able to find out using the Configuration Manager. OK, the issue is not a problem, but only a warning I can neglect even there is no obvious reason for it. Let's turn to more important issues.

[Steven_L_Intel1]

Please attach a ZIP of the .sln file from your solution.

[rase]

Hi Steve, the zip file with the .sln file is attached, as you requested.

[Steven_L_Intel1]

You're right - no Itanium there. Weird. Maybe there's something in one of the C++ project files - not a Fortran problem, obviously.

[rase]

Weird, indeed. After the search for the non-existing Itanium reference I receive a message similar to
1>compilation aborted for D:\Konkar\pycpr5.for (code 1)
for 165 of my subroutines out of more than 1000. I tried to rebuild the whole solution, I deleted manually the content of the directory with objects and exes, nothing helped. I cannot see any reason for that behavior. The files can be edited and stored as usual and are visible in the Explorer tree. Any suggestions what I can do? Reinstallation of the Composer or even VS? Thanks for your help.

[Steven_L_Intel1]

Look in the buildlog.htm - you may have encountered an internal compiler error. The build output pane won't necessarily tell you.

[rase]

The puzzle is solved: During the search for the hidden Itanium I must have changed the environment from Debug to Release. The Release project options contained very old settings which caused the compiler to abort (what should not happen). Switching back to Debug restored the old situation. Sorry for the wasted time. The warning for the mysterious Itanium is still appearing, but I don't care anymore.

[jimdempseyatthecove]

You might try this:

From command prompt and your project folder

notepad YourProjectNameHere.vfproj

The search for "IA64"

If you see any reference, leave notepad open, click on the command prompt window and enter

copy YourProjectNameHere.vfproj YourProjectNameHere_save.vfproj

to save a copy

then back to Notepad and cut out the sections relating to IA64

Caution, .vfproj files are HTML files and the sections are bounded. Example:

  <Configuration Name="Debug|x64">
    <Tool Name="VFFortranCompilerTool" AdditionalOptions="/keep" SuppressStartupBanner="true" DebugInformationFormat="debugEnabled" Optimization="optimizeDisabled" UseProcessorExtensions="codeExclusivelyAVX" Preprocess="preprocessYes" AdditionalIncludeDirectories="..\..\Source\a_toss;..\..\Source\a_goss;..\..\Source\a_ross;..\..\Source\a_foss;..\..\Source\a_boss;..\..\Source\a_avfrt;..\..\Programs\a_avfrt\$(PlatformName)\$(ConfigurationName);..\..\Programs\GlobalData\$(PlatformName)\$(ConfigurationName);..\..\Source\Modules;..\..\Programs\A_Modules\$(PlatformName)\$(ConfigurationName)" PreprocessorDefinitions="_AvFRT;_MOD" EnableEnhancedInstructionSet="codeArchAVX" RealKIND="realKIND8" FloatingPointExceptionHandling="fpe0" Traceback="true" RuntimeChecks="rtChecksAll" BoundsCheck="true" RuntimeLibrary="rtMultiThreadedDebug"/>
    <Tool Name="VFLinkerTool" AdditionalOptions="/machine:x64" LinkIncremental="linkIncrementalNo" SuppressStartupBanner="true" AdditionalLibraryDirectories="C:\Downloads\F90GL\f90gl-1.2.15-ifort\lib64" IgnoreDefaultLibraryNames="libcmtd.lib; libcmt.lib" GenerateDebugInformation="true" SubSystem="subSystemConsole" InterproceduralOptimizations="false" AdditionalDependencies="svml_dispmd.lib ole32.lib oleaut32.lib ..\A_AVFRTControlPanel\$(PlatformName)\$(ConfigurationName)\resource.res f90gl.lib f90glu.lib f90glut.lib"/>
    <Tool Name="VFResourceCompilerTool"/>
    <Tool Name="VFMidlTool" SuppressStartupBanner="true" TargetEnvironment="midlTargetAMD64"/>
    <Tool Name="VFCustomBuildTool"/>
    <Tool Name="VFPreLinkEventTool"/>
    <Tool Name="VFPreBuildEventTool"/>
    <Tool Name="VFPostBuildEventTool"/>
    <Tool Name="VFManifestTool" SuppressStartupBanner="true"/></Configuration>
  <Configuration Name="Release|x64">
    <Tool Name="VFFortranCompilerTool" SuppressStartupBanner="true"/>
    <Tool Name="VFLinkerTool" LinkIncremental="linkIncrementalNo" SuppressStartupBanner="true" SubSystem="subSystemConsole"/>
    <Tool Name="VFResourceCompilerTool"/>
    <Tool Name="VFMidlTool" SuppressStartupBanner="true" TargetEnvironment="midlTargetAMD64"/>
    <Tool Name="VFCustomBuildTool"/>
    <Tool Name="VFPreLinkEventTool"/>
    <Tool Name="VFPreBuildEventTool"/>
    <Tool Name="VFPostBuildEventTool"/></Configuration>

The above has platform x64, yours may have IA64 sprinkled about.

Jim Dempsey

[Steven_L_Intel1]

I looked at this already - no IA64.

[IanH]

Steve Lionel (Intel) wrote:

I looked at this already - no IA64.

Given what was attached - that was in the sln file - would it be worth having a look in the vfproj and vcxproj files too?

[Steven_L_Intel1]

Possibly. Couldn't hurt.