You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@arrow.apache.org by "Antoine Pitrou (JIRA)" <ji...@apache.org> on 2019/02/05 17:12:00 UTC

[jira] [Commented] (ARROW-4485) [CI] Determine maintenance approach to pinned conda-forge binutils package

    [ https://issues.apache.org/jira/browse/ARROW-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761030#comment-16761030 ] 

Antoine Pitrou commented on ARROW-4485:
---------------------------------------

Perhaps we'll be able to use the Anaconda-provided binutils? That's assuming Anaconda is more conservatice than conda-forge...

> [CI] Determine maintenance approach to pinned conda-forge binutils package
> --------------------------------------------------------------------------
>
>                 Key: ARROW-4485
>                 URL: https://issues.apache.org/jira/browse/ARROW-4485
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Wes McKinney
>            Priority: Major
>
> In ARROW-4469 https://github.com/apache/arrow/pull/3554 we pinned binutils 2.31 because the 2.32 release broke builds on Ubuntu Xenial. We aren't sure what will be our path going forward to rely on the conda-forge toolchain because of this



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)