jonkeane commented on issue #49176: URL: https://github.com/apache/arrow/issues/49176#issuecomment-3867297083
> In my opinion, the most realistic options due to this limitation are: > Wait until they upgrade their macOS [runners](https://cran.r-project.org/web/checks/check_flavors.html), since apparently macOS 13 already reached EOL. [[1](https://endoflife.date/macos)] [[2](https://en.wikipedia.org/wiki/MacOS_version_history#Overview)] This is a non-starter for CRAN. They often keep images like these around after EOL, and we have to build on the systems they provide or we will be removed from CRAN. > Go back to using C++-17 standard, since it's more feature complete across all compilers. [[3](https://en.cppreference.com/w/cpp/compiler_support/17.html)] I hope that we can avoid this, but we might need to in order to stay on CRAN until they upgrade their builders. I will admit that I didn't think that the macOS runners + Apple's somewhat bespoke clang was going to be the thing that holds us back on moving to C++20, or I would have raised it on the mailing list when we were discussing this! cc @pitrou > Get a hold of a mac with Xcode 14 and fix the compiler errors. I'm going to try and replicate this locally. It's unfortunate because it won't be automatable, but I haven't found any CI runner (Github Actions or otherwise) that runs MacOS 13. > Create patches based on CRAN logs. The logs are pretty clear what's going on, but without the automatable CI knowing we get it right is hard. -- 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]
