Skip to content
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

[R] LTO job on CRAN fails #29164

Closed
asfimport opened this issue Jul 30, 2021 · 2 comments
Closed

[R] LTO job on CRAN fails #29164

asfimport opened this issue Jul 30, 2021 · 2 comments

Comments

@asfimport
Copy link
Collaborator

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.

@asfimport
Copy link
Collaborator Author

Jonathan Keane / @jonkeane:
Update:

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.

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.

@asfimport
Copy link
Collaborator Author

Neal Richardson / @nealrichardson:
Issue resolved by pull request 10849
#10849

@asfimport asfimport added this to the 6.0.0 milestone Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants