[
https://issues.apache.org/jira/browse/ARROW-10734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17279212#comment-17279212
]
Neal Richardson commented on ARROW-10734:
-----------------------------------------
Updates:
* BDR emailed me about the failing {{grep}}, which means he's trying to get
arrow to run on Solaris again. So we may not be fully out of the woods.
* The recent change to remove boost from parquet had the (I think unrelated)
effect of meaning that the boost we require for building Thrift doesn't have to
build the libraries, which were what failed before. Between that and turning
off jemalloc on solaris (in ARROW-11500) we get a little farther than before
(up to ARROW-11501).
For future testing: From the diff above, just apply the {{quietly <- FALSE}}
change, and then set the version number to match the most recent nightly build
on arrow-r-nightly. Then R CMD build and upload to r-hub, using the non Oracle
Developer Studio Solaris builder.
> [R] Build and test on Solaris
> -----------------------------
>
> Key: ARROW-10734
> URL: https://issues.apache.org/jira/browse/ARROW-10734
> Project: Apache Arrow
> Issue Type: New Feature
> Components: R
> Reporter: Neal Richardson
> Priority: Major
>
> Not that there's demand for Solaris. But if we can actually build on Solaris,
> then we don't need all of the ARROW_R_WITH_ARROW conditional building and
> custom codegen--we can just always build with the C++ library on all of
> CRAN's environments.
> We may already be able to build on Solaris fine, given how many other
> platforms we build Arrow. The bigger challenge may be the CI setup. {{rhub}}
> does have a check_on_solaris
> (https://r-hub.github.io/rhub/reference/check_shortcuts.html) but it's
> unclear if we can call that from a github action. There's also
> https://github.com/vmactions/solaris-vm and related tools for running a VM on
> github actions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
