diff options
| author | Rhys-T <108157737+Rhys-T@users.noreply.github.com> | 2025-04-24 22:46:51 -0400 |
|---|---|---|
| committer | Rhys-T <108157737+Rhys-T@users.noreply.github.com> | 2025-04-24 22:46:51 -0400 |
| commit | 759124776fb54be6c24125d9e9e818a6d9cf5392 (patch) | |
| tree | 5273c16b01f612c87e9ab32b4147917dbdc656c1 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | e406066f94d2cb4a17d708f99bcb892ec2934e12 (diff) | |
mame: replace `sw_vers` with target macOS version
MAME's build system uses `sw_vers` to test whether it needs to link with
the Metal framework or not. However:
a) that would return the build system's version, not the target's, and
b) it can't actually find `sw_vers` in $PATH, so it thinks it's on macOS
version 0, and doesn't link with Metal - causing missing symbol errors
when it gets to the link step, because other parts of the build system
_do_ use the correct target version number.
This replaces the `sw_vers` call with the macOS version actually being
targeted, so everything gets linked correctly.
Based on how be1291e11b3ab0b481471970bffd40385b55a0bf and
2316ada93f48a94f0dd7d2cc7dc5592b3f336a70 resolved a similar
`sw_vers`-related issue.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions