Is there a known issue with building Fortran projects in parallel in Visual Studio 2013?
When I choose to “Rebuild Solution” the build will fail in ifort for seemingly random Fortran projects with “error #10104: unable to open 'C:\Users\{user name}\AppData\Local\Temp\{temporary file name}’”
The temporary file names appear to have the format {4 digit number}tempfile{index number}.
After this build failure, if I choose to “Build Solution” most of the Fortran projects that failed to build in the “Rebuild Solution” operation will build okay, but I may get another error #10104. After the second build failure if I again choose to “Build Solution” the remaining Fortran projects build okay and I get a complete build of my software.
While as a developer I can handle the “Rebuild Solution” failure without much issue by initiating 2 or 3 “Build Solution” passes, our automated build process cannot (and should not need to). I would like to minimize build times using parallel project builds and multiprocessor compilation for our automated builds but it does not seem to work very well.
I am using Visual Studio 2013 and Intel(R) Visual Fortran Composer XE 2013 SP1 Update 1 Integration for Microsoft Visual Studio* 2013, 14.0.0074.12.
My computer’s guts are two Intel Core i5 CPU M 560 @ 2.67Ghz. I have four processors.
My solution contains 60 projects. 28 of them are Fortran projects. The rest are c++ projects.
In Visual Studio\Tools\Options\Projects and Solutions\Build and Run I have a 4 specified for “maximum number of parallel project builds.”
For all 28 of my Fortran projects I have the Property Pages\Fortran\General\Multi-processor Compilation set to “Yes (/MP)”
If I set the maximum number of parallel project builds to one, I do not get the error #10104.
If I set the maximum number of parallel projects to 4 and set the multi-processor compilation to “No” for all of my Fortran projects, I do not get the error #10104.
The other developers on our team also have this issue on their development environments.
I suspect parallel project building and multi-processor compilation is causing ifort to try to open/use temporary files with the same name. Is there a way to me to work around this problem and keep the benefits of parallel project building and multi-processor compilation?