jonkeane commented on code in PR #49221:
URL: https://github.com/apache/arrow/pull/49221#discussion_r2793572830
##########
dev/tasks/r/github.macos.cran.yml:
##########
@@ -58,7 +60,25 @@ jobs:
extra-packages: |
any::rcmdcheck
any::sys
- - name: Install
+ - name: Install MacOSX 11.3 SDK
+ if: matrix.config == 'cran-release'
+ run: |
+ curl -fsSL
https://github.com/phracker/MacOSX-SDKs/releases/download/11.3/MacOSX11.3.sdk.tar.xz
-o /tmp/MacOSX11.3.sdk.tar.xz
+ sudo tar -xf /tmp/MacOSX11.3.sdk.tar.xz -C
/Library/Developer/CommandLineTools/SDKs/
+ echo "Installed MacOSX11.3.sdk to
/Library/Developer/CommandLineTools/SDKs/"
+ ls -la /Library/Developer/CommandLineTools/SDKs/
Review Comment:
The R-devel runners are [already moved to a newer version of the
SDK](https://stat.ethz.ch/pipermail/r-sig-mac/2025-December/015295.html), and
R4.6 should be released in April (historically that's when that happens, but
technically there isn't a set deadline). I don't yet know if that will mean all
of CRAN's builders will have that new SDK though. I imagine they will move
forward soon given how old these are, but in that thread there is a stated
desire to keep supporting macOS + x86, which will
FWIW: I am honestly moderately uncomfortable with this, even in a CI job
that has restricted permissions, etc. etc. But I haven't found any other way to
link against the old SDKs that CRAN is using. We could make this something that
is only run manually (though there is at least one other issue that has been
merged to main that the old SDKs aren't good with:
https://github.com/apache/arrow/pull/49223 /
https://github.com/apache/arrow/pull/49105
I wonder if from ^^^ you have any ideas about how else we might catch when
we need a fallback?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
