From Kurt.Hornik at wu-wien.ac.at  Sun Oct 12 21:12:36 2003
From: Kurt.Hornik at wu-wien.ac.at (Kurt Hornik)
Date: Sun Oct 12 23:22:52 2003
Subject: [Rd] xlc/xlf on osx 
In-Reply-To: <234602B9-FCE5-11D7-B43E-000A95A67E82@stat.ucla.edu>
References: <234602B9-FCE5-11D7-B43E-000A95A67E82@stat.ucla.edu>
Message-ID: <16265.42916.558227.492142@mithrandir.hornik.net>

>>>>> Jan de Leeuw writes:

> I can now build most of R with XLC/XLF using optimization level O4 on
> OS X. I twice have to intervene and manually set optimization to O3
> (for trees.c in zlib and util.c in main). But, more importantly, I
> cannot use the xlc/xlf compiler drivers for linking. They do not
> understand some of the gcc flags, which is no problem because they
> then pass them to ld, but more importantly they refuse to handle any
> file with name foo.lo. Is the "lo" a configure switch I can set to "o"
> ? Currently I am building everything by setting LD_MAIN and LD_SHLIB
> to gcc, i.e. xlc/xlf does the actual compilations and gcc drives the
> linking. This is not ideal, because it may include the wrong options
> and libraries, and it eventually breaks the methods package (which
> refuses to dump code after it compiles).

I think the configure code actually tests whether the compilers can
handle -c -o .lo, and have a workaround if this fails.

-k


[Rd] xlc/xlf on osx
Kurt Hornik