[jira] [Commented] (ARROW-5474) [C++] Document required Boost version

["Wes McKinney (JIRA)" <ji...@apache.org>]

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

Wes McKinney commented on ARROW-5474:
-------------------------------------

So supporting Boost 1.58 comes with a price -- the Flight unit tests depend on Boost.Process which first shipped in Boost 1.64 (which is available in Ubuntu 18.04). I think that building the production libraries with Boost 1.58 is possible, we'll have to set up a Docker build to verify this. I'm working on getting a Xenial 16.04 build with Flight working in the meantime which means vendoring Boost (or installing from PPA)

> [C++] Document required Boost version
> -------------------------------------
>
>                 Key: ARROW-5474
>                 URL: https://issues.apache.org/jira/browse/ARROW-5474
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Neal Richardson
>            Assignee: Wes McKinney
>            Priority: Major
>             Fix For: 0.14.0
>
>
> See debugging on https://issues.apache.org/jira/browse/ARROW-5470. One possible cause for that error is that the local filesystem patch increased the version of boost that we actually require. The boost version (1.54 vs 1.58) was one difference between failure and success. 
> Another point of confusion was that CMake reported two different versions of boost at different times. 
> If we require a minimum version of boost, can we document that better, check for it more accurately in the build scripts, and fail with a useful message if that minimum isn't met? Or something else helpful.
> If the actual cause of the failure was something else (e.g. compiler version), we should figure that out too.



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