472,117 Members | 2,643 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 472,117 software developers and data experts.

Building Python 2.5.2 for Itanium

Hello,

A tool that we use needs to be ported to Itanium. It wsa written
for Python 2.5.2, and so I was happily using the Itanium version of
that release. However, as I have gotten deeper into the port, I see
that ctypes was not included with the Itanium Python 2.5.2 release.

I need to compile that module for that release and platform, but I
have been unable to discover which MS compiler version and runtime was
used to generate the binaries. My understanding is that Python 2.5.2
in general uses Visual Studio 2003, but MS does not appear to have
shipped an Itanium compiler with that version of VS.

I know that there is an Itanium compiler in VS2K5 Team System, and
also a pre-release version was shipped with the Windows 2003 SP1
Platform SDK. However, the compiler in the SDK appears to basically
be an earlier version of the VS2K5 compiler.

When I run setup.py build, the distutils die b/c it is apparently
not the right compiler version.

I am basically looking for some direction w/r to the compiler
environment needed to build modules loadable by Python 2.5.2,
Itanium.

Thanks!
-={C}=-
Nov 21 '08 #1
1 2078
I need to compile that module for that release and platform, but I
have been unable to discover which MS compiler version and runtime was
used to generate the binaries. My understanding is that Python 2.5.2
in general uses Visual Studio 2003, but MS does not appear to have
shipped an Itanium compiler with that version of VS.
That's correct. See PCbuild/readme.txt for (somewhat) detailed
instructions; in essence, you need to use vsextcomp, if you want to
use the official build process.
I know that there is an Itanium compiler in VS2K5 Team System, and
also a pre-release version was shipped with the Windows 2003 SP1
Platform SDK.
I don't think that is a pre-release. The SDK had been shipping with
an Itanium compiler for quite some time, and it is the official compiler
to build binaries for Win64/IA-64 (to my knowledge, it is the compiler
that Windows itself was built with).
However, the compiler in the SDK appears to basically
be an earlier version of the VS2K5 compiler.
That might be. The more critical issue is what CRT to link with.
I had been building the Python Itanium binaries always with the SDK
compiler (of different SDKs, actually); the SDK then would always
link with msvcrt.dll. If you use VS2K5, you might end up linking
with a different CRT, which would be bad.
When I run setup.py build, the distutils die b/c it is apparently
not the right compiler version.
Correct. distutils is not used for building on Windows.

Wrt. the original issue: I am quite skeptical that you can make ctypes
work on Win64/IA-64. There is are several reasons why it wasn't build,
such as it doesn't compile, and, if it would compile, it wouldn't work.
So prepare to do some porting of libffi. Alternatively, rewrite the code
that requires ctypes to use a plain extension module, which is probably
easier to port to Itanium.

Regards,
Martin
Nov 21 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

9 posts views Thread by Dan Cescato | last post: by
2 posts views Thread by Bernhard Mulder | last post: by
reply views Thread by Bernard Delmée | last post: by
8 posts views Thread by Brendan | last post: by
3 posts views Thread by xamdam | last post: by
9 posts views Thread by python | last post: by
1 post views Thread by M.-A. Lemburg | last post: by
14 posts views Thread by csgrimes1 | last post: by
reply views Thread by leo001 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.