[Rd] compile 2.4.1 for linux on power cpus
Prof Brian Ripley
ripley at stats.ox.ac.uk
Thu Mar 15 08:11:34 CET 2007
On Thu, 15 Mar 2007, Peter Dalgaard wrote:
> Andrew Ferris wrote:
>> First off, as you may have guessed, I don't compile many 64 bit programs so thanks again for the help. I'll revert back to powerpc64-unknown-linux-gnu which is the default for -build and -host.
>> Here's the gcc information
>> [hostname]:/ # which gcc
>> [hostname]:/ # gcc -dumpmachine
>> From looking at the GNU documentation for GCC - IBM RS/6000 and PowerPC Options, I see that it mentions this option:
>> Generate code for 32-bit or 64-bit environments of Darwin and SVR4 targets (including GNU/Linux). The 32-bit environment sets int, long and pointer to 32 bits and generates code that runs on any PowerPC variant. The 64-bit environment sets int to 32 bits and long and pointer to 64 bits, and generates code for PowerPC64, as for -mpowerpc64.
>> So would some compiler flags such as these work:
>> 'CC=gcc -m64' 'CXX=g++ -m64' 'FC=gfortran -mc64' 'F77=gfortran -m64' 'LDFLAGS=-L/lib64'
> That's likely. Or use CFLAGS=-m64, and FFLAGS, CXXFLAGS similarly.
The CC etc forms are preferred, as not all configure scripts use the
See the Solaris 64-bit notes in the R-admin manual for proven examples.
> I'd try compiling a simple hello.c program first. Try e.g. "gcc -m64
> hello.c" and see what "file a.out" has to say about the result.
> You may also find yourself having to install a number of packages with
> names like foo-64bit_xx.yy to get 64bit C libraries, but configure
> should tell you about any missing bits in due course, once you have it
> convinced not to build for 32bit.
> R-devel at r-project.org mailing list
Brian D. Ripley, ripley at stats.ox.ac.uk
Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/
University of Oxford, Tel: +44 1865 272861 (self)
1 South Parks Road, +44 1865 272866 (PA)
Oxford OX1 3TG, UK Fax: +44 1865 272595
More information about the R-devel