On Fri, 26 May 2000, Jari Oksanen wrote:
posse at talariainc.com said:
I finally found a way around though the underlying problem persists.
It seems that the problem is with g77. Only the packages using FORTRAN
failed to be loaded correctly in either way (R from rpm or built from
scratch).
The solution was to build R from the source using the flag
All contrib packages installed with this version of R are loaded
correctly and, as far as I can superficially see, work. make check
gives positive feedback.
I am not sure this is safe. At least I was warned when I used a
similar shortcut some years ago when I had some trouble with g77
on MS-DOS (djgpp port). g77 used to apply f2c libraries in her
childhood, but has grown independent since then and so the libraries
forked (libf2c and libf2g). I think that there *may* be a danger of
strange behaviour in some other places if we just resort to drop
in f2c-libraries in g77, and at worst, this behaviour remains undetected.
I think you mean libg2c.a. That's not what --with-f2c does though:
it forces the installation routines to translate Fortran to C and then use
the C compiler on them. That is, it uses f2c not just its libraries.
However, I still don't think this is a good idea. f2c + C accepts lots of
code that is not valid Fortran, so in particular is a bad idea for anyone
developing code. And f2c makes lots of assumptions about how the Fortran
compiler should operate that are not always true of the real compiler.
(Trailing underlines, passing character strings in C style, for two.)
More generally, a real Fortran compiler should generate better code (and