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.
29285 Discussions

ifort: "could not write to argument file"

bigman
Beginner
1,065 Views

I get these errors when I try to compile a fortran source file with Visual Fortran 8.0 (I do have enough disk space on C: and I do have permissions to create and change files in the folders mentioned below):


Compiling...


ifort /nologo /Zi /Od /module:"Debug/" /object:"Debug/" /traceback /check:bounds /libs:static /dbglibs /c /extfor:f "D:ProjectsSUifort: error: could not write to argument file 'C:DOCUME~1AdminLOCALS~1Temp17642.arg'


ifort: error: could not write to argument file 'C:DOCUME~1AdminLOCALS~1Temp17642.arg'


ifort: error: could not write to argument file 'C:DOCUME~1AdminLOCALS~1Temp17642.arg'


fortcom: Severe: No source file on command line


fortcom: Severe: **Internal compiler error: internal abort** Please report this error along with the circumstances in which it occurred in a Software Problem Report. Note: File and line given may not be explicit cause of this error.


Message Edited by BigMan@abv.bg on 12-18-2004 03:06 PM

0 Kudos
3 Replies
Steven_L_Intel1
Employee
1,065 Views
Try it with 8.1 (8.1.025 is current) and see if it still happens. I'm home right now and that particular error doesn't look familiar, but you're using 8.0, so my automatic advice is to try the current version.
0 Kudos
bigman
Beginner
1,065 Views
Could you send me a link so that I can download it?
0 Kudos
Steven_L_Intel1
Employee
1,065 Views
If you have a license entitling you to support, you can get the current version from Intel Premier Support, click on File Downloads in the left column.
But to be honest this error does not sound much like a compiler bug - rather, it looks as if you don't have permission to write into your own Temp folder.
0 Kudos
Reply