> Prof Brian Ripley writes:
> I've some playing with the Intel compilers, currently only on ia32. As
> far as I can see Intel provides compilers for only two OSes and on 50% of
> those -fPIC is wrong so I do think this is really Linux-specific.
> I have put in a Linux-specific change to set
I was somewhat more successful testing the Intel EM64T compilers (on an
Opteron). The masquerading as gcc means the default for CFLAGS is "-g
-O2" which again is problematic: I had to include -mp in all the compiler
flags to ensure that IEC60059 arithmetic was used.
After all that, the Intel c
I've some playing with the Intel compilers, currently only on ia32. As
far as I can see Intel provides compilers for only two OSes and on 50% of
those -fPIC is wrong so I do think this is really Linux-specific.
I have put in a Linux-specific change to set FPICFLAGS, but that is the
least of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear Prof. Ripley,
Prof Brian Ripley schrieb:
| 1) The documented way to specify this is to set FPICFLAGS in
| config.site: see the example in R-admin for the PG compilers. When you
| tried that, what went wrong?
Nothing went wrong. However, I was of
1) The documented way to specify this is to set FPICFLAGS in config.site:
see the example in R-admin for the PG compilers. When you tried that,
what went wrong?
2) It seems strange to specify this for the Fortran compiler and not the C
or C++ compiler.
3) You have suggested the change to a se
Full_Name: Danny van Dyk
Version: R-2.2.0
OS: Gentoo/AMD64
Submission from: (NULL) (83.129.50.65)
I have successfully compiled R-2.2.0 using ifc-9.0.026 on my x86_64 box.
The only (minor) change that hade to be made was adding fpicflags="-fPIC" to
configure.ac in case F77 matches either "ifc" (ol
