I assume what's needed is to install the necessary compiling tools for R packages. Library/Frameworks/R.framework/Resources/bin/config: line 269: make: command not foundĬonfigure: error: in `/private/var/folders/2r/6c5vhb4s3zx3zs4d1dbf9p940000gn/T/Rtmpob4pMm/R.INSTALLd4676ad8595/stringi':Ĭonfigure: error: no acceptable C compiler found in $PATH Library/Frameworks/R.framework/Resources/bin/config: line 153: make: command not found Library/Frameworks/R.framework/Resources/bin/config: line 150: make: command not found yesĬhecking for R < 3.4.0 for CXX1X flag use. Library/Frameworks/R.framework/Resources/bin/RĬhecking for R >= 3.1.0 for C++11 use. Library/Frameworks/R.framework/ResourcesĬhecking for R. ** package ‘stringi’ successfully unpacked and MD5 sums checkedĬhecking for local ICUDT_DIR. ** package ‘scales’ successfully unpacked and MD5 sums checkedĮRROR: compilation failed for package ‘scales’Īnd * installing *source* package ‘stringi’. e.g.: * installing *source* package ‘scales’. When I try to compile packages from source in R, however, I get error messages indicating that I don't have (or that R cannot find) the necessary compiling tools. I installed GNU Fortran, although it's not clear to me whether I need it or not in order to compile R packages. Since binaries of packages are no longer being made for this version, it means that I need to install the latest package versions from source. Looks like 7.2 is the largest TDS protocol version currently supported by FreeTDS but actually 7.2 is more than enough to work with typical data types, including varbinary(max).I'm running Mac OS X 10.7.5 (Lion), which means that the latest version of R I can run is 3.2.1.

Either set it to auto or to a some sensible value: To override this, you have to use the TDS_Version connection string key. It's typically 1433 if you're connecting to a Microsoft® SQL Server™.įreeTDS has an insanely low default TDS protocol version - something like 5.0. You have to use the Port connection string key.Note two caveats applicable to FreeTDS in this sort of setup though: The upside of this approach is that it requires exactly zero configuration of the client machine, other than making sure the FreeTDS ODBC driver is properly installed.

In my opinion, the best way to do is to use a DSN-less configuration - when you encode full information required to connect to a server instance in the ODBC connection string.

Data source name r mac os x