SCM

[#602] 64 bit builds for Mac OS X

Date:
2009-08-23 18:53
Priority:
3
State:
Open
Submitted by:
Peter Cowan (pdc)
Assigned to:
Nobody (None)
Target Version:
None
Summary:
64 bit builds for Mac OS X

Detailed description
I was able to install phylobase using a 64 bit nightly of R, but I was not able to run it (it complains about not being built for the architecture).

install.packages('phylobase', type='source', repos='http://R-Forge.R-project.org') ## seems to work
## but warns: "ld warning: in ncl/ncl/.libs/libncl.a, file is not of required architecture"

require(phylobase) ## fails with

## Error in dyn.load(file, DLLpath = DLLpath, ...) :
## unable to load shared library '/Library/Frameworks/R.framework/Resources/library/phylobase/libs/x86_64/phylobase.so':
## dlopen(/Library/Frameworks/R.framework/Resources/library/phylobase/libs/x86_64/phylobase.so, 6): Symbol not found: __ZN8NxsBlock16GetImpliedBlocksEv
## Referenced from: /Library/Frameworks/R.framework/Resources/library/phylobase/libs/x86_64/phylobase.so
## Expected in: dynamic lookup

R now comes in (experimental?) 64 bit builds for Mac OS X, with the upcoming Mac OS release more users will be interested in running R in 64bit mode.

Comments:

Message  ↓
Date: 2009-09-12 01:42
Sender: Peter Cowan

I went through this all again when I upgraded to Snow Leopard which defaults to 64 bit gcc. Everything apparently worked find for Jim. But, in my case NCL was getting built as 64 bit, while the R version I had and the rest of phylobase were 32 bit.

I suspect that we are not passed R_ARCH to the appropriate NCL makefile.

Date: 2009-08-23 19:33
Sender: Peter Cowan

I'm actually not sure who's issue this is. I've been googling around for a little bit, but I'm far from an expert. The difficulty is that when R is 64bit NCL needs to be built with the proper 64bit CXXFLAGs. However, R can be 32bit or 64bit so we can't just check if the processor is 64bit capable. I think this is all supposed to be handled by the code RCpp made. In short, this is over my head, but there must be a more general sensible solution.

CRAN has started building "Universal" packages that contain both 32 and 64 bit binaries. I don't know if R forge is trying to do the same.

Date: 2009-08-23 18:55
Sender: Ben Bolker

is this an R-forge issue, or a CRAN issue (does CRAN make 64-bit builds?), or our issue? Do we just need to make 64-bit builds available somewhere? What do other packages that include source code do about this?

Attached Files:

Changes

No Changes Have Been Made to This Item

Thanks to:
Vienna University of Economics and Business Powered By FusionForge