I just (finally) upgraded to Mavericks, and I'm having some trouble with RODBC. Once the Mavericks update was done, I upgraded R to 3.1.0, and began reinstalling packages. For RODBC, I got the message that it was unavailable as a binary, only as source. When I try to install as source, the compilation fails with missing headers: configure: error: "ODBC headers sql.h and sqlext.h not found" I do have the up to date Actual Technologies ODBC drivers installed, so I'm not sure what else I'm missing. Additionally, when I download the the OS X binary directly and install it locally, it installs, but segfaults anytime I try to create a connection. Any suggestions?
Trouble Installing RODBC on Mavericks
4 messages · Marc Schwartz, Joran Elias
On Apr 14, 2014, at 12:52 PM, Joran Elias <joran.elias at gmail.com> wrote:
I just (finally) upgraded to Mavericks, and I'm having some trouble with RODBC. Once the Mavericks update was done, I upgraded R to 3.1.0, and began reinstalling packages. For RODBC, I got the message that it was unavailable as a binary, only as source. When I try to install as source, the compilation fails with missing headers: configure: error: "ODBC headers sql.h and sqlext.h not found" I do have the up to date Actual Technologies ODBC drivers installed, so I'm not sure what else I'm missing. Additionally, when I download the the OS X binary directly and install it locally, it installs, but segfaults anytime I try to create a connection. Any suggestions?
You must have installed the Mavericks binary of R 3.1.0 for OSX, which is a logical thing to do. Not all CRAN packages are yet available for that version. You can install the Snow Leopard binary release of 3.1.0 instead and RODBC is available for that version. Regards, Marc Schwartz
I was hoping to avoid the issues others had had compiling packages from source on Mavericks, and I was under the impression that the Mavericks binary of 3.1.0 mostly solved that problem. So I was concerned that even compiling from source failed for me, particularly since it seemed to be a different problem (not finding the sql headers) than the gcc/clang issue. If I installed the Snow Leopard binary of 3.1.0 on a machine running Mavericks, presumably I would have to do the Makevars modification to enable myself to compile packages from source, no? In any case, I have a clone of my machine set up now that I will experiment with installing Mavericks and 3.1.0 and see if I can get RODBC to work somehow.
On Mon, Apr 14, 2014 at 12:16 PM, Marc Schwartz <marc_schwartz at me.com>wrote:
On Apr 14, 2014, at 12:52 PM, Joran Elias <joran.elias at gmail.com> wrote:
I just (finally) upgraded to Mavericks, and I'm having some trouble with RODBC. Once the Mavericks update was done, I upgraded R to 3.1.0, and began reinstalling packages. For RODBC, I got the message that it was unavailable as a binary, only as source. When I try to install as source, the compilation fails with
missing
headers: configure: error: "ODBC headers sql.h and sqlext.h not found" I do have the up to date Actual Technologies ODBC drivers installed, so
I'm
not sure what else I'm missing. Additionally, when I download the the OS X binary directly and install it locally, it installs, but segfaults anytime I try to create a connection. Any suggestions?
You must have installed the Mavericks binary of R 3.1.0 for OSX, which is a logical thing to do. Not all CRAN packages are yet available for that version. You can install the Snow Leopard binary release of 3.1.0 instead and RODBC is available for that version. Regards, Marc Schwartz
Hi Joran, If you want to proceed with building RODBC from source on Mavericks, at least until a binary is available for the Mavericks release of R, you will need to go to iodbc.org and download the sources to get the header files that are missing. Since XCode was updated for Mavericks, the iodbc header files have not been included in the XCode SDK tree. Regards, Marc
On Apr 14, 2014, at 8:50 PM, Joran Elias <joran.elias at gmail.com> wrote:
I was hoping to avoid the issues others had had compiling packages from source on Mavericks, and I was under the impression that the Mavericks binary of 3.1.0 mostly solved that problem. So I was concerned that even compiling from source failed for me, particularly since it seemed to be a different problem (not finding the sql headers) than the gcc/clang issue. If I installed the Snow Leopard binary of 3.1.0 on a machine running Mavericks, presumably I would have to do the Makevars modification to enable myself to compile packages from source, no? In any case, I have a clone of my machine set up now that I will experiment with installing Mavericks and 3.1.0 and see if I can get RODBC to work somehow. On Mon, Apr 14, 2014 at 12:16 PM, Marc Schwartz <marc_schwartz at me.com> wrote: On Apr 14, 2014, at 12:52 PM, Joran Elias <joran.elias at gmail.com> wrote:
I just (finally) upgraded to Mavericks, and I'm having some trouble with RODBC. Once the Mavericks update was done, I upgraded R to 3.1.0, and began reinstalling packages. For RODBC, I got the message that it was unavailable as a binary, only as source. When I try to install as source, the compilation fails with missing headers: configure: error: "ODBC headers sql.h and sqlext.h not found" I do have the up to date Actual Technologies ODBC drivers installed, so I'm not sure what else I'm missing. Additionally, when I download the the OS X binary directly and install it locally, it installs, but segfaults anytime I try to create a connection. Any suggestions?
You must have installed the Mavericks binary of R 3.1.0 for OSX, which is a logical thing to do. Not all CRAN packages are yet available for that version. You can install the Snow Leopard binary release of 3.1.0 instead and RODBC is available for that version. Regards, Marc Schwartz