[
https://issues.apache.org/jira/browse/ARROW-13507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392366#comment-17392366
]
Jonathan Keane commented on ARROW-13507:
----------------------------------------
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.
> [R] LTO job on CRAN fails
> -------------------------
>
> Key: ARROW-13507
> URL: https://issues.apache.org/jira/browse/ARROW-13507
> Project: Apache Arrow
> Issue Type: Bug
> Components: R
> Reporter: Neal Richardson
> Priority: Critical
> Labels: pull-request-available
> Fix For: 6.0.0, 5.0.1
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> 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|https://github.com/wch/r-debug/pull/22] so that we don't have
> to build R from source to test this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
