You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Kouhei Sutou (Jira)" <ji...@apache.org> on 2020/06/19 21:03:00 UTC

[jira] [Assigned] (ARROW-9183) [C++] Failed to build arrow-cpp with gcc 4.9.2

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

Kouhei Sutou reassigned ARROW-9183:
-----------------------------------

    Assignee: Shuai Zhang

> [C++] Failed to build arrow-cpp with gcc 4.9.2
> ----------------------------------------------
>
>                 Key: ARROW-9183
>                 URL: https://issues.apache.org/jira/browse/ARROW-9183
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: C++
>    Affects Versions: 0.17.1
>            Reporter: Shuai Zhang
>            Assignee: Shuai Zhang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.0.0
>
>         Attachments: fix.patch, image-2020-06-19-11-29-13-641.png
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The [Building Arrow C++|https://github.com/apache/arrow/blob/apache-arrow-0.17.1/docs/source/developers/cpp/building.rst] document say "building requires a C++11-enabled compiler. On Linux, gcc 4.8 and higher should be sufficient."
> But actually, it failed to build with gcc 4.9.2 (see attached image-2020-06-19-11-29-13-641.png). This is because a bug in gcc [Bug 57250|https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57250]
> Please note it in the document to lead using a higher version of gcc. Current document is still misleading.
>  
> NEED TRIAGE, because the [atomic_shared_ptr.h|https://github.com/apache/arrow/blob/apache-arrow-0.17.1/cpp/src/arrow/util/atomic_shared_ptr.h] file is aim to eliminate the bug. But the error occurred when compiling it.
> OK, got it. I installed clang but still using the gcc 4.9.2's libstdc++. The bug appeared then.
> I think it more reliable to check libstdc++ version instead of the gcc version, because this is a libstdc++ bug instead of a gcc bug. I found it possible to [check the libstdc++ version via MACRO \_\_GLIBCXX\_\_|https://stackoverflow.com/questions/10354636/how-do-you-find-what-version-of-libstdc-library-is-installed-on-your-linux-mac] with help of [this timeline table|https://gcc.gnu.org/develop.html#timeline].



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