[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Cheryl Sabella added the comment: Closed based on msg323776. -- nosy: +cheryl.sabella resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Michael Osipov <1983-01...@gmx.net> added the comment: Cannot reproduced on master: export LDFLAGS="-L/usr/local/lib/hpux64 +DD64" export CFLAGS=+DD64 Python build finished successfully! The necessary bits to build these optional modules were not found: _bz2 _curses_panel

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Changes by Stefan Krah stefan-use...@bytereef.org: -- nosy: -skrah ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12991 ___ ___ Python-bugs-list

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Changes by Adi Roiban a...@roiban.ro: -- nosy: +adiroiban ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12991 ___ ___ Python-bugs-list mailing

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Wong Wah Meng wahm...@freescale.com added the comment: Good news is now I am still using ld, like what is generated in the Makefile file by configure script, and able to do the linking process for the built-in modules successfully. I only need to set CC=cc +DD64 and CXX=aCC and the process

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Wong Wah Meng wahm...@freescale.com added the comment: Closing the issue. Please contact me if the README file for HP-UX Itanium 64-bit build should be amended. -- status: open - closed ___ Python tracker rep...@bugs.python.org

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Senthil Kumaran sent...@uthcode.com added the comment: Wah Meng and I were discussing about this in a separate thread as well. I think, it is a good idea to improve the Readme for this issue. Wah Meng, since you already went at length to contact HP and clarify linker issue with 64 bit and

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Stefan Krah stefan-use...@bytereef.org added the comment: I think, it is a good idea to improve the Readme for this issue. +1. Wah Meng: Building everything is not enough, does 'make test' complete successfully? For gcc, Python2.7 relies on two critical options, -fno-strict-aliasing and

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Senthil Kumaran sent...@uthcode.com added the comment: Wah meng - Instructions to get the _tkinter compile would be a good idea too. Also, can you verify the same instructions would work for 3.2 version of Python? -- keywords: +patch Added file:

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Wong Wah Meng wahm...@freescale.com added the comment: I think there is something that is not working here at least for the instructions in build README file about setting up 4 environment variables required for HP Itanium 64-bit build using HP compilers. CC=cc

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Stefan Krah stefan-use...@bytereef.org added the comment: The README looks outdated. This isn't surprising, since probably no one here has access to the HP compiler. If you want to improve it, please try this: make distclean ./configure CC=cc CFLAGS=+DD64 make test I don't think the linker

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Wong Wah Meng wahm...@freescale.com added the comment: Thanks! I am gonna try this out again. Actually I noticed this when you mentioned about using cc as the linker front end. I followed instruction in the README file, after I edited Makefile to remove the -O Limit 1500 line, and after

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

New submission from Wong Wah Meng wahm...@freescale.com: Server Info: HP-UX B.11.31 Itanium ia64. Evaluation copy is used however the license is being purchased, hopefully this are not these errors are not caused by evaluation copy. # swlist -l product | grep Compiler ACXX

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Stefan Krah stefan-use...@bytereef.org added the comment: I think you may want to ask these questions on the Python mailing list: http://mail.python.org/mailman/listinfo/python-list This is the Python bug-tracker, and it's not obvious to me that any of your points is a bug in Python.

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Stefan Krah stefan-use...@bytereef.org added the comment: 1) I cannot reproduce this. 2) ld is the linker and not the compiler. 3) and 4) Should definitely be asked on python-list. -- resolution: - works for me stage: - committed/rejected status: open - closed

[issue12991] Python 64-bit build on HP Itanium - Executable built successfully but modules failed with HP Compiler

Martin v. Löwis mar...@v.loewis.de added the comment: I encountered more failures in module build with my HP-UX ANSI C Compiler versus gcc. I wonder why. That's really simple to answer. HP-UX is not well supported. You are pretty much on your own. -- nosy: +loewis