search for: ilaenv

...at.o: No such file or directory gcc.exe: F77_aloc.o: No such file or directory I don't see these entry points in any of the accompanying library files. I hunted around and found the above functions in an old MinGW library libg2c.lib When I link them in, I get different undefined references: ilaenv.o:ilaenv.f:(.text+0x55): undefined reference to `_gfortran_compare_string dlamch.o:dlamch.f:(.text+0x3bf): undefined reference to `_gfortran_pow_r8_i4' dormlq.o:dormlq.f:(.text+0x281): undefined reference to `_gfortran_concat_string Any guidance on how to solve this problem? John Nolan [[al...

Dear All, Under Debian GNU/Linux La.svd (with method = "dgesdd") sometimes gives the error "Error in La.svd(data, nu = 0, nv = min(nrow, ncol), method = "dgesdd") : LAPACK routine DGESDD gave error code -12" It seems not to depend on the data per se, but on the relationship between numbers of rows and columns. For example, if the number of columns is 100,

...ted to passing of strings from C to Fortran. Indeed, BLAS and LAPACK define a large number of subroutines that take one or more explicit single-character strings as arguments. Other than that, BLAS has only one function (xerbla), which takes a string of unspecified length, LAPACK only has four (ilaenv, ilaenv2stage, lsamen, xerbla). The C interfaces to BLAS/LAPACK from Netlib depend on the historic behavior that explicit single-character strings are interoperable, concretely CBLAS and LAPACKE provide C interfaces/code that calls into Fortran BLAS/LAPACK without passing the 1s as lengths of...

Hi, I have tried to pinpoint potential problems which could lead to the LAPACK issues that are currently seen in R. I built the current R trunk using AR=gcc-ar RANLIB=gcc-ranlib ./configure --prefix=$HOME --enable-lto --enable-BLAS-shlib=no --without-recommended-packages and used this to find problem areas. There are quite a few warnings that were flagged, due to mismatches in function