[MacPorts] #59772: python38: fails on Leopard: Undefined symbols: :info:build "_pthread_threadid_np"

[MacPorts]

#59772: python38: fails on Leopard: Undefined symbols: :info:build
"_pthread_threadid_np"
-----------------------+---------------------------
  Reporter:  kencu     |      Owner:  jmroot
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:  leopard tiger
      Port:  python38  |
-----------------------+---------------------------

Comment (by kencu):

 Some resources I accumulated in hopes of coming up with some kind of
 implementation for {{{pthread_threadid_np}}} on < 10.6 that might not be
 total garbage:

 <https://stackoverflow.com/questions/1540603/mac-iphone-is-there-a-way-to-
 get-a-thread-identifier-without-using-objective-c>

 <https://stackoverflow.com/questions/21091000/how-to-get-thread-id-of-a
 -pthread-in-linux-c-program>

 <https://developer.apple.com/library/archive/documentation/General/Conceptual/ConcurrencyProgrammingGuide/ThreadMigration/ThreadMigration.html#//apple_ref/doc/uid/TP40008091-CH105-SW1>

 <https://developer.apple.com/library/archive/documentation/Darwin/Conceptual/KernelProgramming/scheduler/scheduler.html>

 <https://robert.sesek.com/2018/7/debugging_early_program_startup_on_macos.html>

 Alternatively, if none of these are acceptable, it's not the end of the
 world to keep a local Tiger patch here hidden away in MacPorts; these
 threadid's are mostly used for debugging anyway, and goodness help anyone
 who is trying to do some serious debugging on Tiger these days...people
 just want python38 to build so they're not left high and dry...

-- 
Ticket URL: <https://trac.macports.org/ticket/59772#comment:13>
MacPorts <https://www.macports.org/>
Ports system for macOS