Compiling Old Code with Fortran Compiler

[CClist]

I have an old Fortran subroutine code from my school research in 2014 that I would like to compile and it only can be compiled using Intel Fortran Compiler version 11 which comes with Parallel Studio XE 2015 maybe? I tried the newer free version OneAPI  but it does not work in my case (something change in the way it compiles?). 

I looked over the internet for a place to buy a copy of the software but to no avail. I would be very grateful if someone can help point me to a seller that still sells this copy or if Intel release it to public use then can I get a copy? 

[Arjen_Markus]

As the Fortran standard and, even more so the compilers, is remarkably compatible with older versions, what causes your code to be limited to that "ancient" compiler version? Have you tried it with the current compiler or is it a problem with the Visual Studio solution?

If indeed the compiler complains, which is quite possible because checks get better all the time, can you tell us what it complains about?

[CClist]

Thanks for the reply. The subroutine is a UMAT.for file that gets attached to Abaqus job. When Abaqus runs, it looks for the compiler and expects certain variables based on its env variables file. I am hypothesizing those variables have been changed and therefore it outputs error from attempting to connect to OnAPI compiler. 

All I got in the error report is:

Begin Compiling Abaqus/Standard User Subroutines

Intel(R) Fortran Compiler for applications running on Intel(R) 64, Version 2025.1.1 Build 20250418

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

Error: Problem during compilation - C:\Temp\Fortran\UMAT.for.

At least I know the Fortran code syntax is ok otherwise it would have giving me error before compiling. 

Hopefully this sheds light on the issue. 

[jimdempseyatthecove]

I second @Arjen_Markus suggestion to try to compile C:\Temp\Fortran\UMAT.for from the oneAPI command line.

You will also need to determine the compiler options use by Abaqus and use those too.

Note, MS VS creates a build log file. Maybe Abaqus does too. If so, you can inspect the log file for compiler options used as well as error messages issued.

Jim Dempsey

[andrew_4619]

"but it does not work " does not help much but I suspect there are a number of members on the forum that would quickly make it work if you give them something to look at e.g. the errors listing , buidlog.html

[Arjen_Markus]

One way to find out what is going wrong - at least a step on that way - is to compile the source file outside the Abaqus environment. The compiler is found, but apparently any error messages are being replaced by the not-so-helpful message "Problem during compilation". That is not the typical message a compiler prints. By using the compiler directly you will very likely get error messages that are much more to the point. Anfd it would give us some idea of what the problem is.

[CClist]

Thanks Arjen for trying to walk through what is going on but my original question was if you could lead me to place to buy a copy of Intel Fortran Compiler version 11 / Parallel Studio XE 2015 which Abaqus is compatible with. Is there a hope of finding a copy or  it is just out of circulation and I am out of luck? 

[andrew_4619]

Zero chance of getting a copy V11 of that, and you would need a licence which you can't get.

[DavidWhite]

I suggest that you look for resources on the web for linking Abaqus with Fortran.  It is clear that some versions of Abaqus work with Intel OneAPI.

There are also some sites with instructions for editing the batch files that Abaqus uses to match the compiler version.

These resources will be more helpful than anything this list can provide (unless there are Abaqus experts who have tackled the same problem).

I believe that the root cause may be that you are trying to use a too old version of Abaqus which may not work with the latest Intel OneAPI, especially if Abaqus is 32-bit since the latest OneAPI only produces 64-bit executables.

[CClist]

Thanks everyone for the helpful comments.