[ python-Bugs-1307978 ] Unsatisfied symbols: _PyGILState_NoteThreadState (code)

[SourceForge.net]

Bugs item #1307978, was opened at 2005-09-29 14:14
Message generated for change (Comment added) made by mwh
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1307978&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: Python 2.4
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Goetz Isenmann (isenmann)
Assigned to: Michael Hudson (mwh)
Summary: Unsatisfied symbols: _PyGILState_NoteThreadState (code)

Initial Comment:
Compiling python 2.4.2 without threads (for hpux1020)
results
in an undefined symbol _PyGILState_NoteThreadState in
Python/pystate.o.
There are probably some "#ifdef WITH_THREAD"s missing.

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

>Comment By: Michael Hudson (mwh)
Date: 2005-09-30 09:20

Message:
Logged In: YES 
user_id=6656

It's fixed now:

Python/pystate.c revision 2.43
Python/pystate.c revision 2.38.2.4

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

Comment By: Neal Norwitz (nnorwitz)
Date: 2005-09-30 06:31

Message:
Logged In: YES 
user_id=33168

Wasn't a fix for this checked in?  Can this be closed?

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

Comment By: Michael Hudson (mwh)
Date: 2005-09-29 15:04

Message:
Logged In: YES 
user_id=6656

Can you try the attached?

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

Comment By: Reinhold Birkenfeld (birkenfeld)
Date: 2005-09-29 14:32

Message:
Logged In: YES 
user_id=1188172

I'd think that a #ifdef WITH_THREAD around the
_PyGILState_NoteThreadState call in pystate.c:192 is enough.

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

Comment By: Michael Hudson (mwh)
Date: 2005-09-29 14:28

Message:
Logged In: YES 
user_id=6656

Aaargh, I expect you're right.  Should be easy to fix, will have a patch for 
you to test shortly.

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

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