topic Problem with PXFSTAT() function in Intel® Fortran Compiler

Problem with PXFSTAT() function

Evan_de_Kock — Mon, 11 Jan 2010 12:46:28 GMT

Dear All

I have been playing with the Posix library routines (IFPOSIX module)and it seems that the function PXFSTAT() fails when used with file names that contains blank characters, such as "C:\temp\Copy oftest.txt". For this example it returns the error code ENOENT. However, the function PXFACCESS has no problem with the same file name! Is this a bug in the PXFSTAT() function?

Do anybody know why PXFFORK() and most of the posix signal handling routines (e.g., PXFSIGADDSET) are only avaible for Linux and Mac OS? A large chunk of the standard set of posix routines is simply not available on Windows platforms.

I would appreciate any comments or suggestions.
Evan

Problem with PXFSTAT() function

Steven_L_Intel1 — Wed, 20 Jan 2010 20:15:12 GMT

Evan,

I've reported the problem with PXFSTAT as issue DPD200149522 and have asked about the other routines. I'd guess, though, it's because those routines depend on Unix-specific features that don't exist on Windows.

Problem with PXFSTAT() function

Steven_L_Intel1 — Thu, 21 Jan 2010 20:54:04 GMT

Here's what I heard from the developers:

"These routines map to the fork and sigaddset that are supported by the linux and mac oss. There is nothing comparable on Windows. Windows supports only two/three signals (SIGINT, SIGKILL, and SIGALRM?); so, doesnt have the rich set of system routines to support them."

Problem with PXFSTAT() function

Steven_L_Intel1 — Fri, 23 Apr 2010 20:18:49 GMT

The PXFSTAT error is fixed in 11.1 Update 6.