It's possibly the -save-temps that is the problem. Why have you specified that? Also, the .o doesn't go into a temporary directory, by default it goes into your current directory unless you have said something else with -o.
If you can capture the output of each of the scripts it might be handy to add -#x to the ifort line - this will show you all of the generated commands and execute them. This will allow you to see what it is using for temp files.
save-temps is specified, the following occurs: The object .o file (Linux OS and OS X) or .obj file (Windows OS) is saved. *end quote* So this led me to belive that the object files are affected by -save-temps. Is that right? 4. Back to the original question - if multiple ifort processes are launched concurrently, is it possible that different ifort processes will use identical temp file names? If so, I guess the only/best way to avoid this is to set unique TMPDIR for each ifort process? Many thanks for your help Anton
I am going to ask Lorri to comment on this, as she knows this part better than anyone, but she won't see this until at least Tuesday. I would not expect you to have to establish separate temporary directories for parallel builds.
The "driver" is the application that read the command line and invokes the preprocessor, the compiler itself, the assembler, and finally the linker/loader.
The -save-temps switch saves intermediate preprocessed files, object files and any intermediate assembly files (if created). So, in other words, any temporary files created for the user.
Probably not a huge surprise, but the driver creates lots and lots of temporary files for its own use. And, no. We don't save those with the -save-temps switch.
I hope this helps --
Well, I looked at where we issue the error you reported.
We use mkstemp to create/open a temporary file, and if that returns an error, we output the error message you saw.
a colleague of me is also getting the same error
"ifort: error #10295: error generating temporary file name, check disk space and permissions"
even when only typing "ifort" oin the command line. All disks have enough free storage available and the problem also occurrs when running "ifort" from the command line as root.
My colleage asked me if i can help, but after checking the diskspace and the persmissions (as root), i have no idea, what causes this error message.
Do you have a solution?
Best Regards and thank you very much,