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

[Cheryl Sabella]

Cheryl Sabella  added the comment:

Closed based on msg323776.

--
nosy: +cheryl.sabella
resolution:  -> out of date
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Michael Osipov]

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 _gdbm
_lzma _sqlite3  _tkinter
_uuid ossaudiodev   readline
spwd  zlib
To find the necessary bits, look in setup.py in detect_modules() for the 
module's name.


The following modules found by detect_modules() in setup.py, have been
built by the Makefile instead, as configured by the Setup files:
_abc  atexitpwd
time


Failed to build these modules:
_ctypes   _dbm  _elementtree
cmath math  pyexpat


Following modules built successfully but were removed because they could not be 
imported:
_asyncio

running build_scripts
copying and adjusting /var/osipovmi/cpython/Tools/scripts/pydoc3 -> 
build/scripts-3.8
copying and adjusting /var/osipovmi/cpython/Tools/scripts/idle3 -> 
build/scripts-3.8
copying and adjusting /var/osipovmi/cpython/Tools/scripts/2to3 -> 
build/scripts-3.8
changing mode of build/scripts-3.8/pydoc3 from 640 to 755
changing mode of build/scripts-3.8/idle3 from 640 to 755
changing mode of build/scripts-3.8/2to3 from 640 to 755
renaming build/scripts-3.8/pydoc3 to build/scripts-3.8/pydoc3.8
renaming build/scripts-3.8/idle3 to build/scripts-3.8/idle3.8
renaming build/scripts-3.8/2to3 to build/scripts-3.8/2to3-3.8

$ file ./python
./python:   ELF-64 executable object file - IA64
$ ./python
Python 3.8.0a0 (heads/bpo-34412:f1331c0e83, Aug 20 2018, 09:53:38) [C] on 
hp-ux11
Type "help", "copyright", "credits" or "license" for more information.
>>>

The necessary bits are libraries in 64 bit which I have only in 32 bit.
This issue can be closed.

--
nosy: +michael-o

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Stefan Krah]

Changes by Stefan Krah stefan-use...@bytereef.org:


--
nosy:  -skrah

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Adi Roiban]

Changes by Adi Roiban a...@roiban.ro:


--
nosy: +adiroiban

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Wong Wah Meng]

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 make process is 
able to build python executable 64-bit and all the built-in modules where the 
necessary bit can be found.

For other built-in modules, for example, _tkinter, I am also able to build it 
this time by setting these 3 environment variables where ~/local is where I 
installed my tcl/tk binary.

export CC=cc +DD64 -I/home/r32813/local/include
export CXX=aCC
export LDFLAGS=-L/home/r32813/local/lib -lxnet

I am finally able to build python 64-bit and built-in library on HP ia64 using 
HP compiler aCC. Thanks for the input everyone. :)

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Wong Wah Meng]

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
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Senthil Kumaran]

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 found a solution to it, it would be a good idea to 
document it.

Is this the only change for the successful compilation - CC=cc +DD64 and 
CXX=aCC .

If there are more details, you can provide changes to the Readme in the form a 
diff and I shall commit to the trunk.

Thanks!

--
assignee:  - orsenthil
components: +Documentation -Build
nosy: +orsenthil
resolution: works for me - 
status: closed - open
versions: +Python 3.2, Python 3.3

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Stefan Krah]

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 -fwrapv. The HP compiler might need similar options.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Senthil Kumaran]

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: http://bugs.python.org/file23221/README.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Wong Wah Meng]

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
CXX=aCC
BASECFLAGS=+DD64
LDFLAGS=+DD64 -lxnet
When above 4 environment variables are set, the configure script will pick them 
up and build the Makefile that passes in LDFLAGS into the linker. The linker 
doesn't seem to recognize +DD64 on HP-UX. 

ld -b +DD64 -lxnet 
build/temp.hp-ux-B.11.31-ia64-2.7/home/r32813/Build/2.7.1/Python-2.7.1/Modules/mathmodule.o
 
build/temp.hp-ux-B.11.31-ia64-2.7/home/r32813/Build/2.7.1/Python-2.7.1/Modules/_math.o
 -L/usr/local/lib -lm -o build/lib.hp-ux-B.11.31-ia64-2.7/math.so
ld: Unrecognized argument: +DD64
Fatal error.

I did a workaround by only setting CC=cc +DD64 and CXX=aCC and did not set 
the other 2 environment variables, and able to build python 64-bit without the 
failed modules that were due to invalid flag passed into the linker. So I am 
re-opening the issue here to see if this is something we can amend in the 
instruction of README file for HP 64-bit build using HP Compiler.

--
status: closed - open

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Stefan Krah]

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 should be invoked as 'ld'. Several sites
suggest that the HP compiler can be used a the linker front end
(in the same manner as gcc).

http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/ad/r0007656.htm

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Wong Wah Meng]

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 python executable is built, the Makefile is 
overwritten (maybe re-generated by the compiler) again and my changes of -O and 
-Limit 1500 is added back. However that doesn't create big damage like the 
+DD64 to the linker (ld). 

I see. Since I have got HP Compiler, I will provide some updates here once I 
have a newer finding. I have submitted my question of Why ld doesn't recognize 
+DD64 flag to HP and they are checking for me. The progress over there is 
slow. 

Thanks for your reply!

Regards,
Wah Meng

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Wong Wah Meng]

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  C.06.26.EVAL   HP C/aC++ Compiler 
  C-ANSI-C  C.06.26.EVAL   HP C/aC++ Compiler 
  COMPLIBS  B.11.31Compiler Support Libraries 


I encountered more failures in module build with my HP-UX ANSI C Compiler 
versus gcc. I wonder why. I need a Oracle plug-in later, i.e. cx_Oracle and the 
reason I do not want to ignore these errors now because I thought cx_Oracle 
will have to (or, better) be built using HP compiler, not gcc for support from 
Oracle. 

I read through the README file, I followed the instruction to set the required 
environment variables before the configure is run, and unset them before make 
is run, also edited Makefile to remove Optimization and the -Olimit 1500. 
However, it gives me a lot more modules that are failed to be built versus 2 
when gcc is used. At the bottom of the mail we can see what failed to be built. 

I have summarized my inquiry as follow:-
1.) Despite following the instruction to edit the Makefile before make is run, 
I am surprise to see that the Makefile content is changed again when the 
executable is generated. The changed I edited is restored. Is this expected and 
did the compiler make use of the content that I edited when it did the build 
and link? 

$ diff Makefile Makefile_Original
61,62c61,62
 OPT=  -DNDEBUG -O
 BASECFLAGS=   +DD64 -Olimit 1500
---
 OPT=  -DNDEBUG
 BASECFLAGS=   +DD64
 
2.) A lot of failed module and I suspected it is due +DD64 nopt recognized by 
the compiler. Why the HP-UX compiler did not recognize the option? 

ld -b +DD64 -lxnet 
build/temp.hp-ux-B.11.31-ia64-2.7/home/r32813/Build/2.7.1/Python-2.7.1/Modules/mathmodule.o
 
build/temp.hp-ux-B.11.31-ia64-2.7/home/r32813/Build/2.7.1/Python-2.7.1/Modules/_math.o
 -L/usr/local/lib -lm -o build/lib.hp-ux-B.11.31-ia64-2.7/math.so
ld: Unrecognized argument: +DD64
Fatal error.

3.) This is a general question, in the README file there isn't specific 
instruction on how to enable gcc for 64-bit build. Does gcc support 64-bit 
build and how to?

4.) These are warning message. I have seen a lot of them. Am I right I can 
ignore them? I don't see them when I use gcc though. 

cc -Ae -c +DD64 -g -DNDEBUG  -I. -IInclude -I./Include   
-DPy_BUILD_CORE -o Modules/python.o ./Modules/python.c
Include/pyfpe.h, line 8: warning #3750-D: \ followed by white space is not 
a line splice

Thanks in advance for your input. Here is the output of my make using HP C 
compiler. 
 
Python build finished, but the necessary bits to build these modules were not 
found:
_bsddb _curses_curses_panel   
_sqlite3   _ssl   _tkinter
bsddb185   bz2dl  
gdbm   imageoplinuxaudiodev   
ossaudiodevreadline   spwd
sunaudiodevzlib   
To find the necessary bits, look in setup.py in detect_modules() for the 
module's name.


Failed to build these modules:
_bisect_codecs_cn _codecs_hk  
_codecs_iso2022_codecs_jp _codecs_kr  
_codecs_tw _collections   _csv
_ctypes_ctypes_test   _elementtree
_functools _heapq _hotshot
_io_json  _locale 
_lsprof_md5   _multibytecodec 
_multiprocessing   _random_sha
_socket_struct_testcapi   
array  audioopbinascii
cmath  cPicklecrypt   
cStringIO  datetime   dbm 
fcntl  future_builtinsgrp 
itertools  math   mmap
nisoperator   parser  
pyexpatresource   select  
strop  syslog termios 
time   unicodedata

running build_scripts

--
components: Build
messages: 144123
nosy: wah meng
priority: normal
severity: normal
status: open
title: Python 64-bit build on HP Itanium - Executable built successfully but 
modules failed with HP Compiler
type: compile error
versions: Python 2.7

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Stefan Krah]

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.

--
nosy: +skrah

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Stefan Krah]

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

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Martin v . Löwis]

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

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12991
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com