-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
MINOR: [R] Default to bundled re2 build #39514
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my opinion this shouldn't be a MINOR (i.e., make an issue that summarizes the problem we had with CRAN and why this will fix that problem), but I have no problem with its content!
I would also check crossbow submit --group r
to make sure it doesn't introduce problems there.
@@ -26,7 +26,7 @@ add_custom_target(toolchain-tests) | |||
# Accumulate all bundled targets and we will splice them together later as | |||
# libarrow_bundled_dependencies.a so that third party libraries have something | |||
# usable to create statically-linked builds with some BUNDLED dependencies, | |||
# including allocators like jemalloc and mimalloc | |||
# including allocators like jllemalloc and mimalloc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh no that's probably a rebase mix up, I'll remove it.
crossbow submit --group r |
@github-actions crossbow submit --group r |
Revision: d3044bf Submitted crossbow builds: ursacomputing/crossbow @ actions-c0b42ace6a |
The failures are due to #39518 |
I have added some more details and reasoning to the description/commit message for future me ^^ |
This reverts commit 825956b.
### Rationale for this change The CRAN check on `fedora clang devel` builds with clang against libc++ and has a system re2 installed that was build with C++11 ABI which causes linking to fail due to the [abi:cxx11]-symbol annotation on the system version. A user could manually use the bundled build or path hint a clang version of the library. To avoid extra work for the CRAN maintainers we can just default to the bundled build. The re2 build is small enough that users building from source will not really feel the difference and can still opt to use the system re2 via `EXTRA_CMAKE_FLAGS`. ### What changes are included in this PR? Default to use our bundled build to prevent the problems. ### Are these changes tested? On a local dev container replicating the cran env. ### Are there any user-facing changes? Source build now default to use the bundled re2 version, this can be overridden. Authored-by: Jacob Wujciak-Jens <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit f60c281. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 8 possible false positives for unstable benchmarks that are known to sometimes produce them. |
### Rationale for this change The CRAN check on `fedora clang devel` builds with clang against libc++ and has a system re2 installed that was build with C++11 ABI which causes linking to fail due to the [abi:cxx11]-symbol annotation on the system version. A user could manually use the bundled build or path hint a clang version of the library. To avoid extra work for the CRAN maintainers we can just default to the bundled build. The re2 build is small enough that users building from source will not really feel the difference and can still opt to use the system re2 via `EXTRA_CMAKE_FLAGS`. ### What changes are included in this PR? Default to use our bundled build to prevent the problems. ### Are these changes tested? On a local dev container replicating the cran env. ### Are there any user-facing changes? Source build now default to use the bundled re2 version, this can be overridden. Authored-by: Jacob Wujciak-Jens <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
### Rationale for this change The CRAN check on `fedora clang devel` builds with clang against libc++ and has a system re2 installed that was build with C++11 ABI which causes linking to fail due to the [abi:cxx11]-symbol annotation on the system version. A user could manually use the bundled build or path hint a clang version of the library. To avoid extra work for the CRAN maintainers we can just default to the bundled build. The re2 build is small enough that users building from source will not really feel the difference and can still opt to use the system re2 via `EXTRA_CMAKE_FLAGS`. ### What changes are included in this PR? Default to use our bundled build to prevent the problems. ### Are these changes tested? On a local dev container replicating the cran env. ### Are there any user-facing changes? Source build now default to use the bundled re2 version, this can be overridden. Authored-by: Jacob Wujciak-Jens <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
### Rationale for this change The CRAN check on `fedora clang devel` builds with clang against libc++ and has a system re2 installed that was build with C++11 ABI which causes linking to fail due to the [abi:cxx11]-symbol annotation on the system version. A user could manually use the bundled build or path hint a clang version of the library. To avoid extra work for the CRAN maintainers we can just default to the bundled build. The re2 build is small enough that users building from source will not really feel the difference and can still opt to use the system re2 via `EXTRA_CMAKE_FLAGS`. ### What changes are included in this PR? Default to use our bundled build to prevent the problems. ### Are these changes tested? On a local dev container replicating the cran env. ### Are there any user-facing changes? Source build now default to use the bundled re2 version, this can be overridden. Authored-by: Jacob Wujciak-Jens <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
### Rationale for this change The CRAN check on `fedora clang devel` builds with clang against libc++ and has a system re2 installed that was build with C++11 ABI which causes linking to fail due to the [abi:cxx11]-symbol annotation on the system version. A user could manually use the bundled build or path hint a clang version of the library. To avoid extra work for the CRAN maintainers we can just default to the bundled build. The re2 build is small enough that users building from source will not really feel the difference and can still opt to use the system re2 via `EXTRA_CMAKE_FLAGS`. ### What changes are included in this PR? Default to use our bundled build to prevent the problems. ### Are these changes tested? On a local dev container replicating the cran env. ### Are there any user-facing changes? Source build now default to use the bundled re2 version, this can be overridden. Authored-by: Jacob Wujciak-Jens <[email protected]> Signed-off-by: Jacob Wujciak-Jens <[email protected]>
Rationale for this change
The CRAN check on
fedora clang devel
builds with clang against libc++ and has a system re2 installed that was build with C++11 ABI which causes linking to fail due to the [abi:cxx11]-symbol annotation on the system version.A user could manually use the bundled build or path hint a clang version of the library. To avoid extra work for the CRAN maintainers we can just default to the bundled build. The re2 build is small enough that users building from source will not really feel the difference and can still opt to use the system re2 via
EXTRA_CMAKE_FLAGS
.What changes are included in this PR?
Default to use our bundled build to prevent the problems.
Are these changes tested?
On a local dev container replicating the cran env.
Are there any user-facing changes?
Source build now default to use the bundled re2 version, this can be overridden.