Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Windows XP compilation LNK4010

groupw_bench
Beginner
1,798 Views

I'd like to compile a program for 64 bit Windows XP, under Visual Studio 2013. I had previously done that (with IVF 2012) by specifying "Not set" for the linker subsystem and adding /SUBSYSTEM:WINDOWS,"5.01" to the linker command line. This still works with IVF 2015 (2015.1.148) when compiled for 32 bit target systems, but when compiled for 64 bit target systems, this linker warning appears:

  LINK : warning LNK4010: invalid subsystem version number 5.01; default subsystem version assumed

So I deleted the command line statement and set the linker System SubSystem to one of the choices:

  Windows for Windows XP (/SUBSYSTEM:WINDOWS,"5.1")

but I get exactly the same linker error as before, including the reference to version number 5.01 rather than 5.1.

Is it possible to compile for 64 bit Windows XP using IVF 2015 under Visual Studio 2013? If so, how?

I'm running the compiler on a 64 bit Windows 7 system.

0 Kudos
6 Replies
Steven_L_Intel1
Employee
1,798 Views

Use 5.02 for XP64.

0 Kudos
Mark_Lewy
Valued Contributor I
1,798 Views

I think the OP's point is that if you set Linker->SubSystem to "Console for Windows XP (/SUBSYSTEM:CONSOLE,"5.1")" then this results in  LNK4010 when you do an x64 build because the subsystem should be 5.02 for the 64-bit version of XP.

My workaround for this is to set Linker->SubSystem to "Not Set" and add

/SUBSYSTEM:CONSOLE,"5.02"

to the Additional Options on Linker->Command Line

(BTW, I'm using the XE 2015 IDE integration in VS 2012 Professional Update 4)

0 Kudos
Steven_L_Intel1
Employee
1,798 Views

That's what I was trying to get at. You have to use the command line option for this. I will ask that the subsystem property use 5.02 for XP64.

0 Kudos
groupw_bench
Beginner
1,798 Views

Thanks very much!

Roy

0 Kudos
Steven_L_Intel1
Employee
1,798 Views

Escalated as issue DPD200363676. Curiously, the linker considers 5.1 and 5.01 to mean the same thing, similarly 5.2 and 5.02.

0 Kudos
Steven_L_Intel1
Employee
1,798 Views

This will be fixed in the 16.0 compiler product (Parallel Studio XE 2016).

0 Kudos
Reply