[f2py] Difficulties working on 64 bit windows platform.

[David Wainwright]

From: f2py-users-bounces at cens.ioc.ee [mailto:f2py-users-bounces at cens.ioc.ee] On Behalf Of Pearu Peterson
Sent: Thursday, 17 November 2011 7:21 AM
To: For users of the f2py program
Subject: Re: [f2py] Difficulties working on 64 bit windows platform.


On Wed, Nov 16, 2011 at 5:10 AM, David Wainwright <d.wainwright2 at uq.edu.au<mailto:d.wainwright2 at uq.edu.au>> wrote:
Hello,

I'm having difficulty building an f2py extension.
I have 64 bit Windows 7, running intel fortran (composerXE-2011) and am trying to create 64-bit modules to call from python.
I've attached a trace of my input command and the results below
It appears to be finding and using the fortran compiler correctly & building X64 modules,

However, when it tries to link, I get a fatal error indicating that the module machine type 'x64' conflicts with the target machine 'x86'.

It seems that the wrong linker may be being used, but I am unsure, there appears to be an alternative linker available in an /amd64 subdirectory.


Try to define environment variable

  LDSHARED=<path to the linker in /amd64 subdirectory>

and rerun the f2py.py script.

Can anyone provide clues as to where I might look to fix this?


The support for intelvem compiler is defined in

  C:\Python27\Lib\site-packages\numpy\distutils\fcompiler\intel.py

See the end of this file, the last class definition might need an update..

HTH,
Pearu

Thanks for this,
Unfortunately, changing this environment variable didn't invoke a different linker, and the same error was returned.
Should I be looking to make changes to the class definition (IntelEM64VisualFCompiler) to invoke a different linker, or somewhere else in the code?
I've tested this with intel compilers on Linux and it all works well.
Cheers,
David.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://cens.ioc.ee/pipermail/f2py-users/attachments/20111122/f89e8e40/attachment.htm