You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "david-cortes (via GitHub)" <gi...@apache.org> on 2023/05/17 16:29:15 UTC

[GitHub] [arrow] david-cortes opened a new issue, #35640: [R] `arrow::install_arrow()` doesn't use the same compiler arguments as `install.packages`

david-cortes opened a new issue, #35640:
URL: https://github.com/apache/arrow/issues/35640

   ### Describe the bug, including details regarding any error messages, version, and platform.
   
   When running `arrow::install_arrow()` on R, it will not use the exact same compiler and arguments that are set by default when compiling R packages, which tyically include additional library paths compared to the system's compiler.
   
   For a concrete example, in a mac-ARM setup in which one has `apple-clang` from `xcode-select`, a user `Makevars` file like this would succeed in compiling packages with `install.packages`:
   ```
   CFLAGS += -Xclang -fopenmp
   CXXFLAGS += -Xclang -fopenmp
   LDFLAGS += -lomp
   ```
   (plus an additional entry for `CPPFLAGS`)
   
   But this would throw an error when calling `arrow::install_arrow()` due to `-lomp` - instead, one needs to add a `-L` argument to `LDFLAGS` in `Makevars`.
   
   To be clear, the bug report is not _spefically_ about this particular case, but about not using the remainder of the flags that would end up used with `install.packages`.
   
   This is also quite problematic when using a conda-installed R that might have an environment that differs very significantly from the system's default
   
   ### Component(s)
   
   R


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org