[Rcpp-devel] Getting different build commands on Linux vs. Mac OS

Keith O'Hara kth.ohr at gmail.com
Tue May 1 09:45:31 CEST 2018


Unless I'm mistaken, neither are required to install binary packages. Can you check your *source* build setup; try:

curl -O https://cran.r-project.org/src/contrib/RcppArmadillo_0.8.500.0.tar.gz
R CMD INSTALL RcppArmadillo_0.8.500.0.tar.gz

If that goes through without a hitch then it's probably a package issue. Are you using RStudio? Check your build directory for any .Rprofile or .Renviron files, and also check ~/.R/Makevars for errors.

If you can list the required libraries for bamdb, I'm happy to try a build on my end. (I'm lazy to go through the CMake list :-))

Keith

> On May 1, 2018, at 3:07 AM, Evan Biederstedt <evan.biederstedt at gmail.com> wrote:
> 
> I would add, I think clang and gfortran are working correctly, as these are required for `install.packages('RcppArmadillo')` to install properly.
> 
> On Tue, May 1, 2018 at 3:06 AM, Evan Biederstedt <evan.biederstedt at gmail.com> wrote:
> Maybe my Mac OS needs updating...possibly something with XCode, but it's not clear how...
> 
> --- mac OS Sierra 10.12.6
> --- CRAN R 3.4.3
> ---clang & gfortran
> 
> $ clang --version
> Apple LLVM version 9.0.0 (clang-900.0.39.2)
> Target: x86_64-apple-darwin16.7.0
> Thread model: posix
> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
> 
> $ gfortran --version
> GNU Fortran (GCC) 7.1.0
> Copyright (C) 2017 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> I will update once I have access to and try this on several other mac boxes with different specs..
> 
> Thank you to everyone for the help. 
> 
> 
> On Tue, May 1, 2018 at 1:44 AM, Ralf Stubner <ralf.stubner at r-institute.com> wrote:
> 
> Am 30.04.2018 um 23:42 schrieb Evan Biederstedt <evan.biederstedt at gmail.com>:
> 
>> @Ralf
>> 
>> > I had not installed the necessary C library, so unsurprisingly the compilation step already failed. What I find interesting is that in my case "-std=gnu++11“ and "-I../inst/include/" are present in the command line options for clang++. These are also missing from what you quoted and are also a consequence of src/Makevars. It almost looks as if this file got lost on your macOS box …
>> 
>> Interesting....I'm not sure what to make of this of course, but it would be interesting if it was only happening on this macbook. Perhaps OS version or brew could be to blame? I'm not sure what else would be "special" about this macbook....
> 
> On my side that would be
> • macOS high Sierra
> • CRAN R 3.4.4
> • clang and gfortran as recommended by CRAN
> • brew is installed but I do not see how it enters the picture 
> 
> Greetings 
> Ralf 
> 
> 
> _______________________________________________
> Rcpp-devel mailing list
> Rcpp-devel at lists.r-forge.r-project.org
> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel



More information about the Rcpp-devel mailing list