python314-devel: add compatibility patches for macOS < 10.15

[aeiouaeiouaeiouaeiouaeiouaeiou]

Description

Type(s)

• bugfix
• enhancement
• security fix

Tested on

macOS 10.6.8 10K549 x86_64
Xcode 4.2 4C199

Verification

Have you

• followed our Commit Message Guidelines?
• squashed and minimized your commits?
• checked that there aren't other open pull requests for the same change?
• referenced existing tickets on Trac with full URL in commit message?
• checked your Portfile with port lint?
• tried existing tests with sudo port test?
• tried a full install with sudo port -vst install?
• tested basic functionality of all binary files?
• checked that the Portfile's most important variants haven't been broken?

[macportsbot]

Notifying maintainers:
@jmroot for port python314-devel.

[jmroot]

Have you reported these upstream?

[aeiouaeiouaeiouaeiouaeiouaeiou]

@jmroot no, also I don't see them wanting to support legacy versions of macOS.

[barracuda156]

@jmroot no, also I don't see them wanting to support legacy versions of macOS.

As usual, people are just unaware that both buildbots and users exist.

[aeiouaeiouaeiouaeiouaeiouaeiou]

I think I need to do a PRs in the HACL* and KaRaMeL repositories first.

[jmroot]

@jmroot no, also I don't see them wanting to support legacy versions of macOS.

The installers are still nominally built for 10.13+, so they should care about < 10.15 even if they don't care about < 10.9. Things often break in prereleases and I've found they will often accept PRs for regressions on older versions during the alpha period, provided they don't add complexity. These patches are of course not in a form that would be accepted currently.

I'm really not keen on maintaining a patch set forever, so please make the effort with getting fixes in upstream.

[aeiouaeiouaeiouaeiouaeiouaeiou]

Made patches unconditional and written as they would be sent to upstream repositories.
@jmroot @barracuda156

[barracuda156]

@aeiouaeiouaeiouaeiouaeiouaeiou I have no control over what is merged here, but I will run the build on 10.6 from your PR today (adding a correct patch for pthread_threadid_np) and let you know if that works.