-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[C++] Add support for Boost 1.86 #43746
Comments
kou
changed the title
BUG: compilation error with boost 1.86
[C++] Add support for Boost 1.86
Aug 19, 2024
kou
added a commit
to kou/arrow
that referenced
this issue
Aug 20, 2024
boost/process/*.hpp are deprecated since Boost 1.86. And it seems that it also adds backward incompatible change. We need to use boost/process/v2/*.hpp instead. This introduces `arrow::util::Process` for testing. It wraps boost/process/ API. So we don't need to use boost/process/ API directly in our tests.
kou
added a commit
to kou/arrow
that referenced
this issue
Aug 22, 2024
boost/process/*.hpp are deprecated since Boost 1.86. And it seems that it also adds backward incompatible change. We need to use boost/process/v2/*.hpp instead. This introduces `arrow::util::Process` for testing. It wraps boost/process/ API. So we don't need to use boost/process/ API directly in our tests.
kou
added a commit
to kou/arrow
that referenced
this issue
Aug 23, 2024
boost/process/*.hpp are deprecated since Boost 1.86. And it seems that it also adds backward incompatible change. We need to use boost/process/v2/*.hpp instead. This introduces `arrow::util::Process` for testing. It wraps boost/process/ API. So we don't need to use boost/process/ API directly in our tests.
kou
added a commit
to kou/arrow
that referenced
this issue
Aug 29, 2024
boost/process/*.hpp are deprecated since Boost 1.86. And it seems that it also adds backward incompatible change. We need to use boost/process/v2/*.hpp instead. This introduces `arrow::util::Process` for testing. It wraps boost/process/ API. So we don't need to use boost/process/ API directly in our tests.
kou
added a commit
that referenced
this issue
Sep 3, 2024
### Rationale for this change `boost/process/*.hpp` are deprecated since Boost 1.86. And it seems that it also adds backward incompatible change. We need to use `boost/process/v2/*.hpp` instead. ### What changes are included in this PR? This introduces `arrow::util::Process` for testing. It wraps boost/process/ API. So we don't need to use boost/process/ API directly in our tests. We still use the v1 API on Windows because the v2 API doesn't process group and we don't have a workaround for it on Windows. If GCS's testbench doesn't use multiple processes, we can use the v2 API on Windows because we don't need to use process group in our use case. See also: * The v2 API and process group: boostorg/process#259 * GCS's testbench and multiple processes: googleapis/storage-testbench#669 ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: #43746 Lead-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
Issue resolved by pull request 43766 |
mapleFU
pushed a commit
to mapleFU/arrow
that referenced
this issue
Sep 3, 2024
### Rationale for this change `boost/process/*.hpp` are deprecated since Boost 1.86. And it seems that it also adds backward incompatible change. We need to use `boost/process/v2/*.hpp` instead. ### What changes are included in this PR? This introduces `arrow::util::Process` for testing. It wraps boost/process/ API. So we don't need to use boost/process/ API directly in our tests. We still use the v1 API on Windows because the v2 API doesn't process group and we don't have a workaround for it on Windows. If GCS's testbench doesn't use multiple processes, we can use the v2 API on Windows because we don't need to use process group in our use case. See also: * The v2 API and process group: boostorg/process#259 * GCS's testbench and multiple processes: googleapis/storage-testbench#669 ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: apache#43746 Lead-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
zanmato1984
pushed a commit
to zanmato1984/arrow
that referenced
this issue
Sep 6, 2024
### Rationale for this change `boost/process/*.hpp` are deprecated since Boost 1.86. And it seems that it also adds backward incompatible change. We need to use `boost/process/v2/*.hpp` instead. ### What changes are included in this PR? This introduces `arrow::util::Process` for testing. It wraps boost/process/ API. So we don't need to use boost/process/ API directly in our tests. We still use the v1 API on Windows because the v2 API doesn't process group and we don't have a workaround for it on Windows. If GCS's testbench doesn't use multiple processes, we can use the v2 API on Windows because we don't need to use process group in our use case. See also: * The v2 API and process group: boostorg/process#259 * GCS's testbench and multiple processes: googleapis/storage-testbench#669 ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: apache#43746 Lead-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
khwilson
pushed a commit
to khwilson/arrow
that referenced
this issue
Sep 14, 2024
### Rationale for this change `boost/process/*.hpp` are deprecated since Boost 1.86. And it seems that it also adds backward incompatible change. We need to use `boost/process/v2/*.hpp` instead. ### What changes are included in this PR? This introduces `arrow::util::Process` for testing. It wraps boost/process/ API. So we don't need to use boost/process/ API directly in our tests. We still use the v1 API on Windows because the v2 API doesn't process group and we don't have a workaround for it on Windows. If GCS's testbench doesn't use multiple processes, we can use the v2 API on Windows because we don't need to use process group in our use case. See also: * The v2 API and process group: boostorg/process#259 * GCS's testbench and multiple processes: googleapis/storage-testbench#669 ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: apache#43746 Lead-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Sutou Kouhei <[email protected]> Co-authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Compiling arrow 17 (using
-DARROW_BUILD_TESTS=ON
) with the headers from the recently-released boost 1.86 results in compilation errors, see below.Looking at the errors, the key point from the release notes seems to be:
GCC 12
Clang 17
MSVC 19.40
Component(s)
C++
The text was updated successfully, but these errors were encountered: