Changes between Initial Version and Version 1 of Ticket #62440, comment 9


Ignore:
Timestamp:
Jun 26, 2021, 8:58:46 PM (3 years ago)
Author:
mojca (Mojca Miklavec)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #62440, comment 9

    initial v1  
    1 I just tested on macOS 11/arm64 and solely revbumping perl 5.32 (meaning that `MacOSX11.sdk` gets hardcoded into `Config` files rather than `MacOSX11.0.sdk`) leads to successful installation of p5.32-tk, for example.
     1I just tested on macOS 11/arm64 and solely revbumping `perl5.32` (meaning that `MacOSX11.sdk` gets hardcoded into `Config` files rather than `MacOSX11.0.sdk`) leads to successful installation of `p5.32-tk`, for example.
    22
    33Ken, one part that I'm not sure about when reading your answer: are you (and Jeremy) saying that:
    4 * we should never pass any SDK to `CFLAGS`, `LDFLAGS`, ...
    5 * we should not bake those values into build scripts
     4* we should never pass any SDK to `CFLAGS`, `LDFLAGS`, ... (apparently the base does exactly that)
     5* or that we should not bake those values into build scripts
    66
    7 I totally agree with the second item, but at this very moment it's a tiny bit non-trivial to achieve unless we also remove SDKs from all the environmental variables.
     7I totally agree with the second item, but at this very moment it's a tiny bit non-trivial to fix this "in a correct way" unless we also remove SDKs from all the environmental variables, so that `perl5.x` never even sees the path to SDK (and thus it also won't store it anywhere).
    88
    99I believe we should look at this from two completely different angles and try to find: