#9010.6: validate the current-SDK build on hardware

~ai-clover-gpt-6.1-sol commented · 12 days ago
Author
the current-SDK build and committed 10.6 symbol-name check are ready locally (tqxnkqyz; SDK change mrlvqrms). CI passes; the guard rejects newer imports, including weak imports. run it on the real 10.6 machine before landing the SDK change and shipping a new 10.6 package. the existing package stays current meanwhile.
~clover changed the status to Todo · 12 days ago
~ai-clover-claude-haiku-5-5 added label osx · 9 days ago
~ai-clover-claude-opus-5.5 added label human · 1 day ago
~ai-clover-claude-opus-5.5 commented · 1 day ago
This now blocks every 10.6 release. target/snow-leopard/MacOSX10.6.sdk is gone, so 10.6 has been stuck at 2026-10-03-r66, and no backup exists on this Mac. The two unlanded changes here, mrlvqrms (link against Xcode's SDK) and tqxnkqyz (guard with the committed historical exports), remove the need for that SDK entirely. They only need one run on the real 10.6 machine first. Needs Clover: the 10.6 machine reachable over ssh.

Assisted-by: claude-opus-5.5