[R-SIG-Mac] missing symbols in build of Mac-GUI?

Kevin B. Hendricks kevin.hendricks at sympatico.ca
Fri Sep 8 01:49:56 CEST 2006


It must be my mistake then.  I was following the INSTALL file found  
in Mac-GUI and it said that on Mac Intel I was supposed to use the  
Makefile to insure that the correct version of gcc (ie. /usr/local/ 
gcc4.0/bin/*) version was used.

That Makefile seems to be hard coded to make a universal version of  

I was offering patches to that Makefile and other pieces to allow it  
to create R.app that is not universal.

I am a really an old linux/unix programmer and really have never  
worked with xcodebuilder to any real extent and was actually happier  
with the "make" approach.

Sorry for the noise.


On Sep 7, 2006, at 8:57 AM, Simon Urbanek wrote:

> Kevin,
> On Sep 6, 2006, at 7:59 PM, Kevin B. Hendricks wrote:
>> Hi,
>>> Yes - Mac-GUI rev. 3699 now works with the current R-devel.
>> Thanks.  That fixed my problem.
>> BTW: I personally don't like the idea of universal binaries  
>> especially for things I build from svn checkout myself (such as R  
>> on a daily basis). I simply can not see the benefit of having a  
>> ppc set of *.dylib on an i386 machine and visa-versa.  So I hack  
>> modified the Makefile and the R.dep file and the xproject pieces  
>> in Mac-GUI to build an i386 only version of R.app.  It is possible  
>> that otheres feel as I do about universal binaries.
>> So would you be interested in any patches to build Mac-GUI for  
>> only one platform (selectable of course) instead of just the  
>> universal version?
> I'm not quite sure what you mean - selecting "Development" target  
> for example builds current architecture only. Setting the  
> architectures is as easy as checking the target architecture  
> checkbox in Xcode, so I'm not sure what you had to patch ... The  
> project itself can be built either way without modification.
> Cheers,
> Simon

More information about the R-SIG-Mac mailing list