[ https://issues.apache.org/jira/browse/PARQUET-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wes McKinney resolved PARQUET-640. ---------------------------------- Resolution: Fixed Fix Version/s: cpp-0.1 Issue resolved by pull request 125 [https://github.com/apache/parquet-cpp/pull/125] > [C++] Force the use of gcc 4.9 in conda builds > ---------------------------------------------- > > Key: PARQUET-640 > URL: https://issues.apache.org/jira/browse/PARQUET-640 > Project: Parquet > Issue Type: Bug > Components: parquet-cpp > Reporter: Wes McKinney > Assignee: Wes McKinney > Fix For: cpp-0.1 > > > Follow up to PARQUET-638. I did not realize that using the conda-forge > toolchain (which saves us a lot of OS X boilerplate) was globbering our use > of gcc 4.9. until we are statically linking the c++ standard library, we need > to use gcc 4.9 across the board in our binary testing artifacts -- This message was sent by Atlassian JIRA (v6.3.4#6332)