It depends on the scope of what’s required to make them build. The current default SDK on x86_64-darwin is 10.12, but it’s being bumped to 11.0 for 25.05. If any of the updated source releases start requiring 11.x APIs, additional work would be required to backport them.
I’ve hesitated to link it here because the branch should be considered unstable (as in commit ids change almost every push), but these are the source release packages.
Some of the workarounds have required providing replacement implementations of newer APIs, using older versions of some files, adding availability checks, etc. Once both Darwin architectures default to the 11.x SDK, I’d like to drop the compatibility patches for maintainability reasons (to avoid bitrot since they’re mostly conditioned on SDK version).