On Jul 29, 2012, at 01:59 , Simon Urbanek wrote:

> 
> On Jul 27, 2012, at 5:06 PM, Hadley Wickham wrote:
> 
>>> Actually, probably not the issue. You are getting it from one of R's headers
>>> so it may have gotten there while you configured R on your machine.
>> 
>> Which I didn't do, since I got a pre-built binary from CRAN.  I guess
>> I'll try re-installing and hope the problem goes away.
>> 
> 
> What compilers/OS is this? The error comes from the multi-arch header stub so 
> it dispatches depending on the architecture to the actual headers in the arch 
> subdirectories, but the error means that your architecture is not 
> installed/supported. This is rather odd, unless you're trying to use PPC on 
> more recent OS X without Rosetta but even then ... If in doubt, sudo rm -rf 
> /Library/Frameworks/R.framework and re-install R ...
> 

It would appear to be the stock Lion compiler. I can compile biarch with that 
and a current  R. 

As /Library/Frameworks/R.framework/Resources/include/Rconfig.h in its entirety 
is the following, the only obvious way to reach the #error  would be if 
__i386__ somehow got undefined. Or the file itself is corrupted, of course.

-pd

/* This is an automatically generated universal stub for architecture-dependent 
headers. */
#ifdef __i386__
#include "i386/Rconfig.h"
#elif defined __ppc__
#include "ppc/Rconfig.h"
#elif defined __ppc64__
#include "ppc64/Rconfig.h"
#elif defined __x86_64__
#include "x86_64/Rconfig.h"
#elif defined __arm__
#include "arm/Rconfig.h"
#else
#error "Unsupported architecture."
#endif



> Cheers,
> Simon
> 
> ______________________________________________
> R-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

-- 
Peter Dalgaard, Professor,
Center for Statistics, Copenhagen Business School
Solbjerg Plads 3, 2000 Frederiksberg, Denmark
Phone: (+45)38153501
Email: pd....@cbs.dk  Priv: pda...@gmail.com

______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Reply via email to