You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We don't have a CI job that tests with R built with --enable-lto, and AFAICT there is no docker image out there that has one. I will try to get one added to wch/r-debug so that we don't have to build R from source to test this.
I don't think this alone will work — in the PR I've disabled adding this flag in the LTO env and we now get segfaults. I've also tried removing all of these flags totally and built locally and got the same segfaults.
ARROW-13199 added -fno-lto flags to the build (see also ARROW-12853). This likely is the cause of the LTO failure on CRAN: https://www.stats.ox.ac.uk/pub/bdr/LTO/arrow.out so we probably need to back it out.
We don't have a CI job that tests with R built with --enable-lto, and AFAICT there is no docker image out there that has one. I will try to get one added to wch/r-debug so that we don't have to build R from source to test this.
Reporter: Neal Richardson / @nealrichardson
Assignee: Jonathan Keane / @jonkeane
PRs and other links:
Note: This issue was originally created as ARROW-13507. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: