Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29280 Discussions

Once again ... Comilation fails for files with extensions different from .f90

abhimodak
New Contributor I
689 Views

Hi

I think this (issue) happened some time back, then it was fixed buthappens again with update 6; really frustrating considering how basic this is:

Even if the "user-file-extensions" such as (.f95) are defined through Tools --> Options, the compilation fails from VS. One can compile such files using command line with options such as -Tf and /free.

The default from VS project properties is Fortran --> Language --> Source File Format == Use file extension. This will cause compilation failure even if the extension, for example .f95, is defined as a free fromat file through Tools --> Options.

{I find that a work-around is explicitly specifying the Source File Format option for such files. This can be done for many files at once by selecting those files from the project tree --> Source Files, then right click and use properties. The compilation will then be successful with "Project properties" using defaults.}

Abhi

0 Kudos
5 Replies
Steven_L_Intel1
Employee
689 Views
I can't reproduce this. Can you show me a screenshot of the Tools > Options > Intel Visual Fortran > General page and the build log that fails?
0 Kudos
abhimodak
New Contributor I
689 Views
Hi Steve

I have attached two snapshots. I have already shown you that I have added the non-default extensions in a snapshot attached to another post (on broken syntax coloring).

Abhi
0 Kudos
Steven_L_Intel1
Employee
689 Views
Ok - I can reproduce it in VS2010. The /free is not being supplied on the command line. Works in VS2008, though... I'll report it to the developers. Issue ID is DPD200173496.
0 Kudos
Steven_L_Intel1
Employee
689 Views
This has been fixed for as future update (after updatde 7).
0 Kudos
Steven_L_Intel1
Employee
689 Views
Actually, it was fixed in Update 7.
0 Kudos
Reply