-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build on mac os x #1
Comments
This is possibly solved by commit ca8a4af
|
Thanks for getting back to me so quickly. Yes, I did try to post a bug Compiler incompatibilities are possible, but I wouldn't make them the Anyway, R and Rcpp on my system were built with a different compiler and What I have seen a lot of are dynamic linking issue, where a library Anyway, the modifications you made do solve the .so vs. dylib problem, /usr/local/bin/g++-4.9 dlopen(/Library/Frameworks/R.framework/Versions/3.1/Resources/library/RcppOctave/libs/RcppOctave.so,
|
This is yet another error though. |
Just updating this --- As of today, with some changes by Renaud, RcppOctave no longer has the dylib/so problem on Mac OS. I have gotten it to compile and run quite well when both R and Octave are made with the same toolchain. I've tested successfully with (a) the CRAN build of R and homebrew package installation of Octave, and (b) R and octave both built by hand using gcc 4.9. I was not able to get RcppOctave running when they were built with different toolchains, but I have not tested it with the latest revision. |
The build seems to assume installation of octave by home-brew because, the configure file says, it "works out of box."
It no longer works out of box; this may be related to flux in the home-brew fortran compiler. In addition, many of the octave suggested extensions (e.g., hdf5) are either currently missing from home-brew, or have compilation issues (e.g., openblas).
I've tried octave from home-brew, building octave myself, and the binary download. The only variant that works consistently and has the ordinary extensions is the binary download.
Even when octave is installed successfully, by home-brew or the binary (and if necessary directed to the binary home by configure directives), RcppOctave fails to install because it looks for liboctinterp.so, when both home-brew and the binary install only liboctinterp.dylib.
I suggest adjusting RcppOctave's build requirements so it looks for octave in multiple locations, including the current home-brew, build-from-source into /usr/local/, and works with the .dylib.
Here's the furthest I could get with compilation:
installing to /Library/Frameworks/R.framework/Versions/3.1/Resources/library/RcppOctave/libs
** R
** demo
** exec
** inst
** preparing package for lazy loading
** help
Error : /private/var/folders/s1/_v14lsc56tv44hm304m07vn40000gq/T/RtmpWBGJlA/R.INSTALL15e583ce00d60/RcppOctave/man/o_addpath.Rd:41: .onLoad failed in loadNamespace() for 'RcppOctave', details:
call: FUN(c("/usr/local/octave/3.8.0/lib/octave/3.8.0/liboctinterp.so",
error: unable to load shared object '/usr/local/octave/3.8.0/lib/octave/3.8.0/liboctinterp.so':
dlopen(/usr/local/octave/3.8.0/lib/octave/3.8.0/liboctinterp.so, 6): image not found
ERROR: installing Rd objects failed for package ‘RcppOctave’
The text was updated successfully, but these errors were encountered: