[Python-bugs-list] [ python-Bugs-473150 ] configure weaknesses on HP-UX

noreply@sourceforge.net noreply@sourceforge.net
Sat, 20 Oct 2001 18:02:15 -0700


Bugs item #473150, was opened at 2001-10-20 06:39
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=473150&group_id=5470

Category: Build
Group: Python 2.2
Status: Closed
Resolution: Accepted
Priority: 5
Submitted By: Michael Piotrowski (mxp)
Assigned to: Guido van Rossum (gvanrossum)
Summary: configure weaknesses on HP-UX

Initial Comment:
1. configure doesn't handle HP-UX release numbers
(e.g., B.11.00), resulting in MACHDEP = "hpuxB".

2. After checking for wchar.h, configure doesn't
include it when checking the size of wchar_t.

(Python 2.2b1 on HP-UX 11.00)


----------------------------------------------------------------------

>Comment By: Guido van Rossum (gvanrossum)
Date: 2001-10-20 18:02

Message:
Logged In: YES 
user_id=6380

Do the tests for threads pass? (test_thread.py,
test_threading.py, test_threaded_import.py,
test_threadedtempfile.py) That would be great news!

If there are any other problems on HP-UX, it would be great
if you could help out. Do you know what those problems are?

----------------------------------------------------------------------

Comment By: Michael Piotrowski (mxp)
Date: 2001-10-20 08:41

Message:
Logged In: YES 
user_id=354556

Thist patch has no effect on threads.  However, threads do
work (i.e., are recognized by configure) on HP-UX 11 since
2.2b1 (I just wanted to submit a patch to the 2.2a4
configure.in when 2.2b1 was released).  I am willing to
support you regarding HP-UX, if necessary (there still seem
to be some open issues).


----------------------------------------------------------------------

Comment By: Guido van Rossum (gvanrossum)
Date: 2001-10-20 07:23

Message:
Logged In: YES 
user_id=6380

Thanks! Checked into CVS.

With this patch, do threads work on your system? (We've had
long-standing complaints that Python can't be built with
threads on HP-UX 11, but these are hard to verify for us. It
would be great if we could say with confidence that this is
fixed in 2.2b2.)

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=473150&group_id=5470