[
https://issues.apache.org/jira/browse/ARROW-6793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16948725#comment-16948725
]
Thomas Schm commented on ARROW-6793:
------------------------------------
The new version is breaking my Dockerfile. Here's some output:
Step 6/6 : RUN install2.r --error --deps TRUE arrow
---> Running in 16553854c478
trying URL
'https://mran.microsoft.com/snapshot/2019-09-19/src/contrib/arrow_0.14.1.1.tar.gz'
Content type 'application/octet-stream' length 105910 bytes (103 KB)
==================================================
downloaded 103 KB
* installing *source* package ‘arrow’ ...
** package ‘arrow’ successfully unpacked and MD5 sums checked
** using staged installation
Arrow C++ libraries found via pkg-config
PKG_CFLAGS=-DNDEBUG -DARROW_R_WITH_ARROW
PKG_LIBS=-larrow -lparquet
** libs
g++ -std=gnu++11 -I"/usr/local/lib/R/include" -DNDEBUG -DNDEBUG
-DARROW_R_WITH_ARROW -I"/usr/local/lib/R/site-library/Rcpp/include"
-I/usr/local/include -fvisibility=hidden -fpic -g -O2 -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -c
array.cpp -o array.o
g++ -std=gnu++11 -I"/usr/local/lib/R/include" -DNDEBUG -DNDEBUG
-DARROW_R_WITH_ARROW -I"/usr/local/lib/R/site-library/Rcpp/include"
-I/usr/local/include -fvisibility=hidden -fpic -g -O2 -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -c
array__to_vector.cpp -o array__to_vector.o
array__to_vector.cpp:22:35: fatal error: arrow/util/task-group.h: No such file
or directory
#include <arrow/util/task-group.h>
^
compilation terminated.
make: *** [array__to_vector.o] Error 1
/usr/local/lib/R/etc/Makeconf:176: recipe for target 'array__to_vector.o' failed
ERROR: compilation failed for package ‘arrow’
* removing ‘/usr/local/lib/R/site-library/arrow’
The downloaded source packages are in
‘/tmp/downloaded_packages’
Error: installation of package ‘arrow’ had non-zero exit status
In addition: Warning message:
In install.packages(pkgs, ...) :
installation of package ‘arrow’ had non-zero exit status
ERROR: Service 'r' failed to build: The command '/bin/sh -c install2.r --error
--deps TRUE arrow' returned a non-zero code: 1
/home/thomas/github/antarctic/r/Makefile:23: recipe for target 'build' failed
> [R] Arrow C++ binary packaging for Linux
> ----------------------------------------
>
> Key: ARROW-6793
> URL: https://issues.apache.org/jira/browse/ARROW-6793
> Project: Apache Arrow
> Issue Type: Improvement
> Components: R
> Reporter: Neal Richardson
> Assignee: Neal Richardson
> Priority: Major
> Fix For: 1.0.0
>
>
> Our current installation experience on Linux isn't ideal. Unless you've
> already installed the Arrow C++ library, when you install the R package, you
> get a shell that tells you to install the C++ library. That was a useful
> approach to allow us to get the package on CRAN, which makes it easy for
> macOS and Windows users to install, but it doesn't improve the installation
> experience for Linux users. This is an impediment to adoption of arrow not
> only by users but also by package maintainers who might want to depend on
> arrow.
> macOS and Windows have a better experience because at installation time, the
> configure scripts download and statically link a prebuilt C++ library. CRAN
> bundles the whole thing up and delivers that as a binary R package.
> Python wheels do a similar thing: they're binaries that contain all external
> dependencies. And there are pyarrow wheels for Linux. This suggests that we
> could do something similar for R: build a generic Linux binary of the C++
> library and download it in the R package configure script at install time.
> I experimented with using the Arrow C++ binaries included in the Python
> wheels in R. See discussion at the end of ARROW-5956. This worked on macOS
> (not useful for R, but it proved the concept) and almost worked on Linux, but
> it turned out that the "manylinux2010" standard is too archaic to work with
> contemporary Rcpp.
> Proposal: do a similar workflow to what the manylinux2010 pyarrow build does,
> just with slightly more modern compiler/settings. Publish that C++ binary
> package to bintray. Then download it in the R configure script if a
> local/system package isn't found.
> Once we have a basic version working, test against various distros on
> [R-hub|https://builder.r-hub.io/advanced] to make sure we're solid everywhere
> and/or ensure the current fallback behavior when we encounter a distro that
> this doesn't work for. If necessary, we can make multiple flavors of this C++
> binary for debian, centos, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
