GH-49176: [C++] CRAN build fail on missing std::floating_point concept by jonkeane · Pull Request #49221 · apache/arrow

jonkeane · 2026-02-11T04:15:27Z

Rationale for this change

Passing builds on CRAN

What changes are included in this PR?

A workaround for C++20 compatibility issues

Are these changes tested?

Yes, we can ship these tests in this PR or we can keep them in #49216 either is fine by me.

Are there any user-facing changes?

No

GitHub Issue: [C++] CRAN build fail on missing std::floating_point concept #49176

jonkeane · 2026-02-11T04:15:48Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:17:56Z

Revision: 5ed5de1

Submitted crossbow builds: ursacomputing/crossbow @ actions-bc3fd4369a

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T04:41:38Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:43:49Z

Revision: 1314042

Submitted crossbow builds: ursacomputing/crossbow @ actions-cf07311e56

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T05:06:27Z

cc @shashbha14 here is a fix (+ a CI job that proves it)

jonkeane · 2026-02-11T05:59:25Z

+ 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/


Downloading this from this github site is very funky, and honestly a little sketchy. But it does actually replicate the very old macosx sdks that CRAN is building arrow with. And we can replicate it in CI

Do you have a timeline on when we can remove this?

The R-devel runners are already moved to a newer version of the SDK, 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: #49223 / #49105
I wonder if from ^^^ you have any ideas about how else we might catch when we need a fallback?

cc @kou about the CI aspect of this

Not sure if this is helpful, but I did find https://developer.apple.com/xcode/cpp/#c++20 which lists when some of these features were supported (though not particularly consistently!) and once we are on xcode 14, it looks like we should be clear.

Do we have any macos self-hosted runners? If yes, then just let me know where to put it and how to point this CI at those and I'll make it so...

Ok I have changed this to point to a (private) repo and added a limited PAT to crossbow for just that repo.

Oops, sorry when I commented I hadn't pushed yet, but it is now.

I'm OK with the private repository approach because this is a temporary need. We will be able to remove this after this April.

Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

shashbha14 · 2026-02-11T10:29:31Z

Thanks for working through this and wiring up the macOS-as-CRAN CI job, this makes the situation much clearer.
My earlier attempt on #49176 was just switching to std::is_floating_point_v, but your PR plus the SDK-based CI reproducer is a much more complete solution for the CRAN builders.
I’ll treat this PR as the canonical fix for the issue and won’t push additional changes on top of it unless you’d like help with anything specific.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

jonkeane · 2026-02-13T18:20:26Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-13T18:22:38Z

Revision: 08daa2e

Submitted crossbow builds: ursacomputing/crossbow @ actions-ca0a264fc8

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-13T19:05:30Z

This is ready for (re)-review. If we are going to merge the CI changes (from #49216) we should merge them here, (though we will also need to merge #49223 to have this not fail on main once it is merged, but that's ok cause these are nightly tests)

jonkeane · 2026-02-16T04:57:24Z

I'm going to merge this tomorrow unless there is objection.

pitrou

Thanks a lot @jonkeane !

raulcd · 2026-02-16T08:19:13Z

+ 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/


Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

…concept (apache#49221) ### Rationale for this change Passing builds on CRAN ### What changes are included in this PR? A workaround for C++20 compatibility issues ### Are these changes tested? Yes, we can ship these tests in this PR or we can keep them in apache#49216 either is fine by me. ### Are there any user-facing changes? No * GitHub Issue: apache#49176 Authored-by: Jonathan Keane <jkeane@gmail.com> Signed-off-by: Nic Crane <thisisnic@gmail.com>

jonkeane · 2026-02-11T04:15:27Z

Rationale for this change

Passing builds on CRAN

What changes are included in this PR?

A workaround for C++20 compatibility issues

Are these changes tested?

Yes, we can ship these tests in this PR or we can keep them in #49216 either is fine by me.

Are there any user-facing changes?

No

GitHub Issue: [C++] CRAN build fail on missing std::floating_point concept #49176

jonkeane · 2026-02-11T04:15:48Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:17:56Z

Revision: 5ed5de1

Submitted crossbow builds: ursacomputing/crossbow @ actions-bc3fd4369a

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T04:41:38Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:43:49Z

Revision: 1314042

Submitted crossbow builds: ursacomputing/crossbow @ actions-cf07311e56

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T05:06:27Z

cc @shashbha14 here is a fix (+ a CI job that proves it)

jonkeane · 2026-02-11T05:59:25Z

+ 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/


Downloading this from this github site is very funky, and honestly a little sketchy. But it does actually replicate the very old macosx sdks that CRAN is building arrow with. And we can replicate it in CI

Do you have a timeline on when we can remove this?

The R-devel runners are already moved to a newer version of the SDK, 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: #49223 / #49105
I wonder if from ^^^ you have any ideas about how else we might catch when we need a fallback?

cc @kou about the CI aspect of this

Not sure if this is helpful, but I did find https://developer.apple.com/xcode/cpp/#c++20 which lists when some of these features were supported (though not particularly consistently!) and once we are on xcode 14, it looks like we should be clear.

Do we have any macos self-hosted runners? If yes, then just let me know where to put it and how to point this CI at those and I'll make it so...

Ok I have changed this to point to a (private) repo and added a limited PAT to crossbow for just that repo.

Oops, sorry when I commented I hadn't pushed yet, but it is now.

I'm OK with the private repository approach because this is a temporary need. We will be able to remove this after this April.

Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

shashbha14 · 2026-02-11T10:29:31Z

Thanks for working through this and wiring up the macOS-as-CRAN CI job, this makes the situation much clearer.
My earlier attempt on #49176 was just switching to std::is_floating_point_v, but your PR plus the SDK-based CI reproducer is a much more complete solution for the CRAN builders.
I’ll treat this PR as the canonical fix for the issue and won’t push additional changes on top of it unless you’d like help with anything specific.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

jonkeane · 2026-02-13T18:20:26Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-13T18:22:38Z

Revision: 08daa2e

Submitted crossbow builds: ursacomputing/crossbow @ actions-ca0a264fc8

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-13T19:05:30Z

This is ready for (re)-review. If we are going to merge the CI changes (from #49216) we should merge them here, (though we will also need to merge #49223 to have this not fail on main once it is merged, but that's ok cause these are nightly tests)

jonkeane · 2026-02-16T04:57:24Z

I'm going to merge this tomorrow unless there is objection.

pitrou

Thanks a lot @jonkeane !

raulcd · 2026-02-16T08:19:13Z

+ 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/


Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

…concept (apache#49221) ### Rationale for this change Passing builds on CRAN ### What changes are included in this PR? A workaround for C++20 compatibility issues ### Are these changes tested? Yes, we can ship these tests in this PR or we can keep them in apache#49216 either is fine by me. ### Are there any user-facing changes? No * GitHub Issue: apache#49176 Authored-by: Jonathan Keane <jkeane@gmail.com> Signed-off-by: Nic Crane <thisisnic@gmail.com>

jonkeane · 2026-02-11T04:15:27Z

Rationale for this change

Passing builds on CRAN

What changes are included in this PR?

A workaround for C++20 compatibility issues

Are these changes tested?

Yes, we can ship these tests in this PR or we can keep them in #49216 either is fine by me.

Are there any user-facing changes?

No

GitHub Issue: [C++] CRAN build fail on missing std::floating_point concept #49176

jonkeane · 2026-02-11T04:15:48Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:17:56Z

Revision: 5ed5de1

Submitted crossbow builds: ursacomputing/crossbow @ actions-bc3fd4369a

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T04:41:38Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:43:49Z

Revision: 1314042

Submitted crossbow builds: ursacomputing/crossbow @ actions-cf07311e56

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T05:06:27Z

cc @shashbha14 here is a fix (+ a CI job that proves it)

jonkeane · 2026-02-11T05:59:25Z

+ 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/


Downloading this from this github site is very funky, and honestly a little sketchy. But it does actually replicate the very old macosx sdks that CRAN is building arrow with. And we can replicate it in CI

Do you have a timeline on when we can remove this?

The R-devel runners are already moved to a newer version of the SDK, 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: #49223 / #49105
I wonder if from ^^^ you have any ideas about how else we might catch when we need a fallback?

cc @kou about the CI aspect of this

Not sure if this is helpful, but I did find https://developer.apple.com/xcode/cpp/#c++20 which lists when some of these features were supported (though not particularly consistently!) and once we are on xcode 14, it looks like we should be clear.

Do we have any macos self-hosted runners? If yes, then just let me know where to put it and how to point this CI at those and I'll make it so...

Ok I have changed this to point to a (private) repo and added a limited PAT to crossbow for just that repo.

Oops, sorry when I commented I hadn't pushed yet, but it is now.

I'm OK with the private repository approach because this is a temporary need. We will be able to remove this after this April.

Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

shashbha14 · 2026-02-11T10:29:31Z

Thanks for working through this and wiring up the macOS-as-CRAN CI job, this makes the situation much clearer.
My earlier attempt on #49176 was just switching to std::is_floating_point_v, but your PR plus the SDK-based CI reproducer is a much more complete solution for the CRAN builders.
I’ll treat this PR as the canonical fix for the issue and won’t push additional changes on top of it unless you’d like help with anything specific.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

jonkeane · 2026-02-13T18:20:26Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-13T18:22:38Z

Revision: 08daa2e

Submitted crossbow builds: ursacomputing/crossbow @ actions-ca0a264fc8

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-13T19:05:30Z

This is ready for (re)-review. If we are going to merge the CI changes (from #49216) we should merge them here, (though we will also need to merge #49223 to have this not fail on main once it is merged, but that's ok cause these are nightly tests)

jonkeane · 2026-02-16T04:57:24Z

I'm going to merge this tomorrow unless there is objection.

pitrou

Thanks a lot @jonkeane !

raulcd · 2026-02-16T08:19:13Z

+ 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/


Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

…concept (apache#49221) ### Rationale for this change Passing builds on CRAN ### What changes are included in this PR? A workaround for C++20 compatibility issues ### Are these changes tested? Yes, we can ship these tests in this PR or we can keep them in apache#49216 either is fine by me. ### Are there any user-facing changes? No * GitHub Issue: apache#49176 Authored-by: Jonathan Keane <jkeane@gmail.com> Signed-off-by: Nic Crane <thisisnic@gmail.com>

jonkeane · 2026-02-11T04:15:27Z

Rationale for this change

Passing builds on CRAN

What changes are included in this PR?

A workaround for C++20 compatibility issues

Are these changes tested?

Yes, we can ship these tests in this PR or we can keep them in #49216 either is fine by me.

Are there any user-facing changes?

No

GitHub Issue: [C++] CRAN build fail on missing std::floating_point concept #49176

jonkeane · 2026-02-11T04:15:48Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:17:56Z

Revision: 5ed5de1

Submitted crossbow builds: ursacomputing/crossbow @ actions-bc3fd4369a

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T04:41:38Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:43:49Z

Revision: 1314042

Submitted crossbow builds: ursacomputing/crossbow @ actions-cf07311e56

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T05:06:27Z

cc @shashbha14 here is a fix (+ a CI job that proves it)

jonkeane · 2026-02-11T05:59:25Z

+ 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/


Downloading this from this github site is very funky, and honestly a little sketchy. But it does actually replicate the very old macosx sdks that CRAN is building arrow with. And we can replicate it in CI

Do you have a timeline on when we can remove this?

The R-devel runners are already moved to a newer version of the SDK, 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: #49223 / #49105
I wonder if from ^^^ you have any ideas about how else we might catch when we need a fallback?

cc @kou about the CI aspect of this

Not sure if this is helpful, but I did find https://developer.apple.com/xcode/cpp/#c++20 which lists when some of these features were supported (though not particularly consistently!) and once we are on xcode 14, it looks like we should be clear.

Do we have any macos self-hosted runners? If yes, then just let me know where to put it and how to point this CI at those and I'll make it so...

Ok I have changed this to point to a (private) repo and added a limited PAT to crossbow for just that repo.

Oops, sorry when I commented I hadn't pushed yet, but it is now.

I'm OK with the private repository approach because this is a temporary need. We will be able to remove this after this April.

Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

shashbha14 · 2026-02-11T10:29:31Z

Thanks for working through this and wiring up the macOS-as-CRAN CI job, this makes the situation much clearer.
My earlier attempt on #49176 was just switching to std::is_floating_point_v, but your PR plus the SDK-based CI reproducer is a much more complete solution for the CRAN builders.
I’ll treat this PR as the canonical fix for the issue and won’t push additional changes on top of it unless you’d like help with anything specific.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

jonkeane · 2026-02-13T18:20:26Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-13T18:22:38Z

Revision: 08daa2e

Submitted crossbow builds: ursacomputing/crossbow @ actions-ca0a264fc8

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-13T19:05:30Z

This is ready for (re)-review. If we are going to merge the CI changes (from #49216) we should merge them here, (though we will also need to merge #49223 to have this not fail on main once it is merged, but that's ok cause these are nightly tests)

jonkeane · 2026-02-16T04:57:24Z

I'm going to merge this tomorrow unless there is objection.

pitrou

Thanks a lot @jonkeane !

raulcd · 2026-02-16T08:19:13Z

+ 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/


Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

…concept (apache#49221) ### Rationale for this change Passing builds on CRAN ### What changes are included in this PR? A workaround for C++20 compatibility issues ### Are these changes tested? Yes, we can ship these tests in this PR or we can keep them in apache#49216 either is fine by me. ### Are there any user-facing changes? No * GitHub Issue: apache#49176 Authored-by: Jonathan Keane <jkeane@gmail.com> Signed-off-by: Nic Crane <thisisnic@gmail.com>

jonkeane · 2026-02-11T04:15:27Z

Rationale for this change

Passing builds on CRAN

What changes are included in this PR?

A workaround for C++20 compatibility issues

Are these changes tested?

Yes, we can ship these tests in this PR or we can keep them in #49216 either is fine by me.

Are there any user-facing changes?

No

GitHub Issue: [C++] CRAN build fail on missing std::floating_point concept #49176

jonkeane · 2026-02-11T04:15:48Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:17:56Z

Revision: 5ed5de1

Submitted crossbow builds: ursacomputing/crossbow @ actions-bc3fd4369a

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T04:41:38Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:43:49Z

Revision: 1314042

Submitted crossbow builds: ursacomputing/crossbow @ actions-cf07311e56

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T05:06:27Z

cc @shashbha14 here is a fix (+ a CI job that proves it)

jonkeane · 2026-02-11T05:59:25Z

+ 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/


Downloading this from this github site is very funky, and honestly a little sketchy. But it does actually replicate the very old macosx sdks that CRAN is building arrow with. And we can replicate it in CI

Do you have a timeline on when we can remove this?

The R-devel runners are already moved to a newer version of the SDK, 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: #49223 / #49105
I wonder if from ^^^ you have any ideas about how else we might catch when we need a fallback?

cc @kou about the CI aspect of this

Not sure if this is helpful, but I did find https://developer.apple.com/xcode/cpp/#c++20 which lists when some of these features were supported (though not particularly consistently!) and once we are on xcode 14, it looks like we should be clear.

Do we have any macos self-hosted runners? If yes, then just let me know where to put it and how to point this CI at those and I'll make it so...

Ok I have changed this to point to a (private) repo and added a limited PAT to crossbow for just that repo.

Oops, sorry when I commented I hadn't pushed yet, but it is now.

I'm OK with the private repository approach because this is a temporary need. We will be able to remove this after this April.

Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

shashbha14 · 2026-02-11T10:29:31Z

Thanks for working through this and wiring up the macOS-as-CRAN CI job, this makes the situation much clearer.
My earlier attempt on #49176 was just switching to std::is_floating_point_v, but your PR plus the SDK-based CI reproducer is a much more complete solution for the CRAN builders.
I’ll treat this PR as the canonical fix for the issue and won’t push additional changes on top of it unless you’d like help with anything specific.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

jonkeane · 2026-02-13T18:20:26Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-13T18:22:38Z

Revision: 08daa2e

Submitted crossbow builds: ursacomputing/crossbow @ actions-ca0a264fc8

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-13T19:05:30Z

This is ready for (re)-review. If we are going to merge the CI changes (from #49216) we should merge them here, (though we will also need to merge #49223 to have this not fail on main once it is merged, but that's ok cause these are nightly tests)

jonkeane · 2026-02-16T04:57:24Z

I'm going to merge this tomorrow unless there is objection.

pitrou

Thanks a lot @jonkeane !

raulcd · 2026-02-16T08:19:13Z

+ 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/


Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

…concept (apache#49221) ### Rationale for this change Passing builds on CRAN ### What changes are included in this PR? A workaround for C++20 compatibility issues ### Are these changes tested? Yes, we can ship these tests in this PR or we can keep them in apache#49216 either is fine by me. ### Are there any user-facing changes? No * GitHub Issue: apache#49176 Authored-by: Jonathan Keane <jkeane@gmail.com> Signed-off-by: Nic Crane <thisisnic@gmail.com>

jonkeane · 2026-02-11T04:15:27Z

Rationale for this change

Passing builds on CRAN

What changes are included in this PR?

A workaround for C++20 compatibility issues

Are these changes tested?

Yes, we can ship these tests in this PR or we can keep them in #49216 either is fine by me.

Are there any user-facing changes?

No

GitHub Issue: [C++] CRAN build fail on missing std::floating_point concept #49176

jonkeane · 2026-02-11T04:15:48Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:17:56Z

Revision: 5ed5de1

Submitted crossbow builds: ursacomputing/crossbow @ actions-bc3fd4369a

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T04:41:38Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:43:49Z

Revision: 1314042

Submitted crossbow builds: ursacomputing/crossbow @ actions-cf07311e56

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T05:06:27Z

cc @shashbha14 here is a fix (+ a CI job that proves it)

jonkeane · 2026-02-11T05:59:25Z

+ 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/


Downloading this from this github site is very funky, and honestly a little sketchy. But it does actually replicate the very old macosx sdks that CRAN is building arrow with. And we can replicate it in CI

Do you have a timeline on when we can remove this?

The R-devel runners are already moved to a newer version of the SDK, 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: #49223 / #49105
I wonder if from ^^^ you have any ideas about how else we might catch when we need a fallback?

cc @kou about the CI aspect of this

Not sure if this is helpful, but I did find https://developer.apple.com/xcode/cpp/#c++20 which lists when some of these features were supported (though not particularly consistently!) and once we are on xcode 14, it looks like we should be clear.

Do we have any macos self-hosted runners? If yes, then just let me know where to put it and how to point this CI at those and I'll make it so...

Ok I have changed this to point to a (private) repo and added a limited PAT to crossbow for just that repo.

Oops, sorry when I commented I hadn't pushed yet, but it is now.

I'm OK with the private repository approach because this is a temporary need. We will be able to remove this after this April.

Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

shashbha14 · 2026-02-11T10:29:31Z

Thanks for working through this and wiring up the macOS-as-CRAN CI job, this makes the situation much clearer.
My earlier attempt on #49176 was just switching to std::is_floating_point_v, but your PR plus the SDK-based CI reproducer is a much more complete solution for the CRAN builders.
I’ll treat this PR as the canonical fix for the issue and won’t push additional changes on top of it unless you’d like help with anything specific.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

jonkeane · 2026-02-13T18:20:26Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-13T18:22:38Z

Revision: 08daa2e

Submitted crossbow builds: ursacomputing/crossbow @ actions-ca0a264fc8

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-13T19:05:30Z

This is ready for (re)-review. If we are going to merge the CI changes (from #49216) we should merge them here, (though we will also need to merge #49223 to have this not fail on main once it is merged, but that's ok cause these are nightly tests)

jonkeane · 2026-02-16T04:57:24Z

I'm going to merge this tomorrow unless there is objection.

pitrou

Thanks a lot @jonkeane !

raulcd · 2026-02-16T08:19:13Z

+ 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/


Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

…concept (apache#49221) ### Rationale for this change Passing builds on CRAN ### What changes are included in this PR? A workaround for C++20 compatibility issues ### Are these changes tested? Yes, we can ship these tests in this PR or we can keep them in apache#49216 either is fine by me. ### Are there any user-facing changes? No * GitHub Issue: apache#49176 Authored-by: Jonathan Keane <jkeane@gmail.com> Signed-off-by: Nic Crane <thisisnic@gmail.com>

jonkeane · 2026-02-11T04:15:27Z

Rationale for this change

Passing builds on CRAN

What changes are included in this PR?

A workaround for C++20 compatibility issues

Are these changes tested?

Yes, we can ship these tests in this PR or we can keep them in #49216 either is fine by me.

Are there any user-facing changes?

No

GitHub Issue: [C++] CRAN build fail on missing std::floating_point concept #49176

jonkeane · 2026-02-11T04:15:48Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:17:56Z

Revision: 5ed5de1

Submitted crossbow builds: ursacomputing/crossbow @ actions-bc3fd4369a

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T04:41:38Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:43:49Z

Revision: 1314042

Submitted crossbow builds: ursacomputing/crossbow @ actions-cf07311e56

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T05:06:27Z

cc @shashbha14 here is a fix (+ a CI job that proves it)

jonkeane · 2026-02-11T05:59:25Z

+ 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/


Downloading this from this github site is very funky, and honestly a little sketchy. But it does actually replicate the very old macosx sdks that CRAN is building arrow with. And we can replicate it in CI

Do you have a timeline on when we can remove this?

The R-devel runners are already moved to a newer version of the SDK, 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: #49223 / #49105
I wonder if from ^^^ you have any ideas about how else we might catch when we need a fallback?

cc @kou about the CI aspect of this

Not sure if this is helpful, but I did find https://developer.apple.com/xcode/cpp/#c++20 which lists when some of these features were supported (though not particularly consistently!) and once we are on xcode 14, it looks like we should be clear.

Do we have any macos self-hosted runners? If yes, then just let me know where to put it and how to point this CI at those and I'll make it so...

Ok I have changed this to point to a (private) repo and added a limited PAT to crossbow for just that repo.

Oops, sorry when I commented I hadn't pushed yet, but it is now.

I'm OK with the private repository approach because this is a temporary need. We will be able to remove this after this April.

Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

shashbha14 · 2026-02-11T10:29:31Z

Thanks for working through this and wiring up the macOS-as-CRAN CI job, this makes the situation much clearer.
My earlier attempt on #49176 was just switching to std::is_floating_point_v, but your PR plus the SDK-based CI reproducer is a much more complete solution for the CRAN builders.
I’ll treat this PR as the canonical fix for the issue and won’t push additional changes on top of it unless you’d like help with anything specific.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

jonkeane · 2026-02-13T18:20:26Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-13T18:22:38Z

Revision: 08daa2e

Submitted crossbow builds: ursacomputing/crossbow @ actions-ca0a264fc8

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-13T19:05:30Z

This is ready for (re)-review. If we are going to merge the CI changes (from #49216) we should merge them here, (though we will also need to merge #49223 to have this not fail on main once it is merged, but that's ok cause these are nightly tests)

jonkeane · 2026-02-16T04:57:24Z

I'm going to merge this tomorrow unless there is objection.

pitrou

Thanks a lot @jonkeane !

raulcd · 2026-02-16T08:19:13Z

+ 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/


Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

…concept (apache#49221) ### Rationale for this change Passing builds on CRAN ### What changes are included in this PR? A workaround for C++20 compatibility issues ### Are these changes tested? Yes, we can ship these tests in this PR or we can keep them in apache#49216 either is fine by me. ### Are there any user-facing changes? No * GitHub Issue: apache#49176 Authored-by: Jonathan Keane <jkeane@gmail.com> Signed-off-by: Nic Crane <thisisnic@gmail.com>

jonkeane · 2026-02-11T04:15:27Z

Rationale for this change

Passing builds on CRAN

What changes are included in this PR?

A workaround for C++20 compatibility issues

Are these changes tested?

Yes, we can ship these tests in this PR or we can keep them in #49216 either is fine by me.

Are there any user-facing changes?

No

GitHub Issue: [C++] CRAN build fail on missing std::floating_point concept #49176

jonkeane · 2026-02-11T04:15:48Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:17:56Z

Revision: 5ed5de1

Submitted crossbow builds: ursacomputing/crossbow @ actions-bc3fd4369a

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T04:41:38Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-11T04:43:49Z

Revision: 1314042

Submitted crossbow builds: ursacomputing/crossbow @ actions-cf07311e56

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-11T05:06:27Z

cc @shashbha14 here is a fix (+ a CI job that proves it)

jonkeane · 2026-02-11T05:59:25Z

+ 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/


Downloading this from this github site is very funky, and honestly a little sketchy. But it does actually replicate the very old macosx sdks that CRAN is building arrow with. And we can replicate it in CI

Do you have a timeline on when we can remove this?

The R-devel runners are already moved to a newer version of the SDK, 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: #49223 / #49105
I wonder if from ^^^ you have any ideas about how else we might catch when we need a fallback?

cc @kou about the CI aspect of this

Not sure if this is helpful, but I did find https://developer.apple.com/xcode/cpp/#c++20 which lists when some of these features were supported (though not particularly consistently!) and once we are on xcode 14, it looks like we should be clear.

Do we have any macos self-hosted runners? If yes, then just let me know where to put it and how to point this CI at those and I'll make it so...

Ok I have changed this to point to a (private) repo and added a limited PAT to crossbow for just that repo.

Oops, sorry when I commented I hadn't pushed yet, but it is now.

I'm OK with the private repository approach because this is a temporary need. We will be able to remove this after this April.

Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

shashbha14 · 2026-02-11T10:29:31Z

Thanks for working through this and wiring up the macOS-as-CRAN CI job, this makes the situation much clearer.
My earlier attempt on #49176 was just switching to std::is_floating_point_v, but your PR plus the SDK-based CI reproducer is a much more complete solution for the CRAN builders.
I’ll treat this PR as the canonical fix for the issue and won’t push additional changes on top of it unless you’d like help with anything specific.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

jonkeane · 2026-02-13T18:20:26Z

@github-actions crossbow submit test-r-macos-as-cran

github-actions · 2026-02-13T18:22:38Z

Revision: 08daa2e

Submitted crossbow builds: ursacomputing/crossbow @ actions-ca0a264fc8

Task	Status
test-r-macos-as-cran

jonkeane · 2026-02-13T19:05:30Z

This is ready for (re)-review. If we are going to merge the CI changes (from #49216) we should merge them here, (though we will also need to merge #49223 to have this not fail on main once it is merged, but that's ok cause these are nightly tests)

jonkeane · 2026-02-16T04:57:24Z

I'm going to merge this tomorrow unless there is objection.

pitrou

Thanks a lot @jonkeane !

raulcd · 2026-02-16T08:19:13Z

+ 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/


Sorry missed this
Do we have any macos self-hosted runners?
No, we only have the CUDA self-hosted runners. Unfortunately it's also not easy adding self-hosted macOS runners as the current runs-on solution we use to set up self-hosted runners doesn't seem to support macOS runners: https://runs-on.com/runners/macos/

…concept (apache#49221) ### Rationale for this change Passing builds on CRAN ### What changes are included in this PR? A workaround for C++20 compatibility issues ### Are these changes tested? Yes, we can ship these tests in this PR or we can keep them in apache#49216 either is fine by me. ### Are there any user-facing changes? No * GitHub Issue: apache#49176 Authored-by: Jonathan Keane <jkeane@gmail.com> Signed-off-by: Nic Crane <thisisnic@gmail.com>

jonkeane requested review from assignUser, kou and raulcd as code owners February 11, 2026 04:15

github-actionsBot added the awaiting committer review Awaiting committer review label Feb 11, 2026

github-actionsBot added the Component: C++ label Feb 11, 2026

apache deleted a comment from github-actionsBotFeb 11, 2026

jonkeane force-pushed the gh49176-std-floatingpoint-workaround branch from 1314042 to dc11decCompare February 11, 2026 04:46

jonkeane requested a review from pitrou February 11, 2026 05:05

jonkeane commented Feb 11, 2026
View reviewed changes

github-actionsBot added awaiting changes Awaiting changes and removed awaiting committer review Awaiting committer review labels Feb 11, 2026

jonkeane mentioned this pull request Feb 12, 2026
GH-48593: [C++] C++20: use standard calendar / timezone APIs #48601
Merged

jonkeaneand others added 3 commits February 13, 2026 12:17

macos 11 sdk from jonkeane/crossbow
751daf0

Workaround on older partially compliant C++20 implementations
3cf3c71

linting
08daa2e
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

jonkeane force-pushed the gh49176-std-floatingpoint-workaround branch from dc11dec to 08daa2eCompare February 13, 2026 18:19

github-actionsBot added awaiting change review Awaiting change review and removed awaiting changes Awaiting changes labels Feb 13, 2026

apache deleted a comment from github-actionsBotFeb 13, 2026

github-actionsBot added awaiting changes Awaiting changes and removed awaiting change review Awaiting change review labels Feb 13, 2026

jonkeane requested a review from rok February 13, 2026 19:05

jonkeane mentioned this pull request Feb 14, 2026
GH-49287: [C++][R] Clean up any other C++20 partial compatibility issues #49223
Merged

jonkeane requested a review from thisisnic February 14, 2026 15:41

pitrou approved these changes Feb 16, 2026
View reviewed changes

raulcd approved these changes Feb 16, 2026
View reviewed changes

github-actionsBot added awaiting merge Awaiting merge and removed awaiting changes Awaiting changes labels Feb 16, 2026

thisisnic merged commit 1d76e1e into apache:mainFeb 16, 2026
59 checks passed

thisisnic removed the awaiting merge Awaiting merge label Feb 16, 2026

thisisnic mentioned this pull request Feb 16, 2026
[C++] CRAN build fail on missing std::floating_point concept #49176
Closed

jonkeane mentioned this pull request Feb 16, 2026
MINOR: try to use r-universe's testing #49216
Closed

thisisnic mentioned this pull request Feb 18, 2026
[R] CRAN packaging checklist for version 23.0.1 #49322
Closed
37 tasks

thisisnic mentioned this pull request May 6, 2026
[R] Update macOS CRAN job SDK from 11.3 to 14.5 to match R 4.6.0 build environment #49941
Closed