[R] R and package don't know they're built on same system

[Liaw, Andy]

One thing to make sure is that all compilers used match; i.e., all 32-bit or
all 64-bit.  On our SLES8 pre-installed on Opteron, g++ was left out of the
64-bit toolchain.  R itself compiled fine (as 64-bit), but some packages
failed to install.  It was strange because the packages were built, but
failed to load.  I was only able to track it down because I happen to know
that the packages that failed contain C++ code, so they were compiled with
the 32-bit g++, and thus cannot be loaded into 64-bit R.

HTH,
Andy

> From: Ross Boylan
> 
> I just had the interesting experience of building a package and R on
> the same system, and having R refuse to load the resultant dynamic
> library because it was thought to be for a different system.
> 
> The system was non-standard and beta, being a Linux-based 64 bit
> Opteron system.  It uses the gnu tool chain.  The dynamic library was
> built from C source.
> 
> When I tried to load the library R (1.8.1) complained
> "package Rpmi was built for i686-pc-linux-gnu"
> Inspection of R.version$platform, which is the thing the i686.... is
> being compared to, shows that it is x86_64-unknown-linux-gnu.
> 
> I worked around this by removing the test causing the error (in
> library.R), but, considering I built both R and Rmpi (an unofficial
> version 0.4.6 from the author) within minutes of each other, it was
> very surprising to find they had different notions of their system.
> 
> Any idea what's behind this, or how to fix it?
> 
> ______________________________________________
> R-help at stat.math.ethz.ch mailing list
> https://www.stat.math.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide! 
> http://www.R-project.org/posting-guide.html
> 
> 


------------------------------------------------------------------------------
Notice:  This e-mail message, together with any attachments,...{{dropped}}