You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Krisztian Szucs (Jira)" <ji...@apache.org> on 2020/04/10 19:17:00 UTC

[jira] [Resolved] (ARROW-8388) [C++] GCC 4.8 fails to move on return

     [ https://issues.apache.org/jira/browse/ARROW-8388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krisztian Szucs resolved ARROW-8388.
------------------------------------
    Resolution: Fixed

Issue resolved by pull request 6894
[https://github.com/apache/arrow/pull/6894]

> [C++] GCC 4.8 fails to move on return
> -------------------------------------
>
>                 Key: ARROW-8388
>                 URL: https://issues.apache.org/jira/browse/ARROW-8388
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: C++
>    Affects Versions: 0.16.0
>            Reporter: Ben Kietzman
>            Assignee: Ben Kietzman
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.17.0
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> See https://github.com/apache/arrow/pull/6883#issuecomment-611661733
> This is a recurring problem which usually shows up as a broken nightly (the gandiva nightly jobs, specifically) along with similar issues due to gcc 4.8's incomplete handling of c++11. As long as someone depends on these we should probably have an every-commit CI job which checks we haven't introduced such a breakage



--
This message was sent by Atlassian Jira
(v8.3.4#803005)