Trond Hasle Amundsen
2005-Sep-01 12:26 UTC
[R] Using non-gcc compilers with install.packages()
Hi, I have built R 2.1.1 on Solaris and OSF1, and used the operating system's native compiler set. This worked fine. However, when I try using install.packages() it insists on using g77 etc., which doesn't exist on those systems. How can I specify which compilers to use? What about other compile-time options like LDFLAGS etc.? NB! Please include me in the CC list, since I'm not a mailinglist member. PS. I really like perl's approach to module building. When building perl modules, it defaults to the same compilers as perl was initially built with. This seems like a sane approach also for R IMHO. Cheers, -- Trond Hasle Amundsen <t.h.amundsen at usit.uio.no> Center for Information Technology Services, University of Oslo
On Thu, 1 Sep 2005, Trond Hasle Amundsen wrote:> > Hi, > > I have built R 2.1.1 on Solaris and OSF1, and used the operating > system's native compiler set. This worked fine. However, when I try > using install.packages() it insists on using g77 etc., which doesn't > exist on those systems. > > How can I specify which compilers to use? What about other > compile-time options like LDFLAGS etc.? > > NB! Please include me in the CC list, since I'm not a mailinglist > member. > > PS. I really like perl's approach to module building. When building > perl modules, it defaults to the same compilers as perl was initially > built with. This seems like a sane approach also for R IMHO.Indeed, R is pretty sane. Fine tuning is conveniently carried out by editing the config.site file in the root source directory; LDFLAGS are on line 138 of the released 2.1.1 source. Which particular packages have you found showing this behaviour?> > Cheers, > >-- Roger Bivand Economic Geography Section, Department of Economics, Norwegian School of Economics and Business Administration, Helleveien 30, N-5045 Bergen, Norway. voice: +47 55 95 93 55; fax +47 55 95 95 43 e-mail: Roger.Bivand at nhh.no