ARROW-17406: [C++] Failing to build the C++ Lib with tests

[kshitij12345]

Ref: https://issues.apache.org/jira/browse/ARROW-17406

Pin boost-cpp to a version which doesn't raise warning.

[github-actions[bot]]

https://issues.apache.org/jira/browse/ARROW-17406

[github-actions[bot]]

:warning: Ticket has no components in JIRA, make sure you assign one.

[github-actions[bot]]

:warning: Ticket has not been started in JIRA, please click 'Start Progress'.

[kou]

We can use C++14 by specifying -DCMAKE_CXX_STANDARD=14.

[kshitij12345]

@kou Do other parts of the library support c++14?
(Also are you suggesting to add this flag to the build snippet on the webpage that walks through the build process?)

[kou]

Yes. We have CI jobs for C++14 and C++17.

If our documents miss it, could you update our documents?

[kshitij12345]

Sure. Will look into that. Thanks @kou !

[pitrou]

@kou Can we get this merged quickly to resolve CI failures?

[kou]

Which CI failures are you thinking? There are many CI failures for now (oh...) but it seems that there are no CI failures related to this.

[pitrou]

Sorry, I mean that merging this PR allows to fix AppVeyor, so we should do it quickly.

[kou]

Ah, I see. But this is not a real fix. This is just a workaround.

I'll take a look at the CI failure tomorrow. Please wait for a while. If you can't wait, you can merge this.

[pitrou]

Unblocking AppVeyor would be nice. As for the real fix, there is now some hope that we move to C++17 soon.

[kshitij12345]

Besides updating the doc, nothing actionable for me right? Thanks :)

cc: @pitrou @kou

[kou]

Continuous discussion about AppVeyor failure: https://github.com/apache/arrow/pull/13903

(I think that we can fix the AppVeyor failure by removing CI jobs on AppVeyor instead of merging this change.)