I'm observing that the new staged installation in R 3.6.0 can produce:
mv: cannot move
‘/home/alice/R/x86_64-pc-linux-gnu-library/3.6/00LOCK-codetools/00new/codetools’
to ‘/home/alice/R/x86_64-pc-linux-gnu-library/3.6/codetools’: File
exists
ERROR: moving to final location failed
on some file s
Hi Steve,
With the caveat that one may need to use the VALUE attribute to
account for pass-by-value vs pass-by-reference.
LAPACK should be all pass by reference, it is old F77-style
code (except that the odd ALLOCATABLE array has snuck in
in the testing routines).
Hi Peter,
we (the gfortran team) are currently discussing this at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90329 . I
invite everybody who has an interest in this topic to
take part in the discussion there.
Workarounds/solutions include:
- disable certain optimizations -- works for now, but
The point is that LAPACK uses characters as control arguments in multiple
places and we don't write the LAPACK Fortran routines. It has long been known
that general character strings was a portability issue but many (not just R
people) have thought that length-one character were safe to pass as
Hi, Thomas, Tomas,
Doesn't this issue demonstrate the warning and advice given in the last
paragraph of section 6.6
of the "Writing R Extensions" manual:
Passing character strings from C to Fortran or vice versa is not portable (and
to Fortran 90 or later is even less so). We have found that
