search for: use_fc_len_t

...internals.h. (Neither are part of the API.) PACKAGE INSTALLATION: * Header Rconfig.h contains the value of FC_LEN_T deduced at installation which is used by the prototypes in headers R_ext/BLAS.h and R_ext/Lapack.h but to avoid extensive breakage this is only exposed when USE_FC_LEN_T is defined. If a package's C/C++ calls to BLAS/LAPACK allow for the 'hidden' arguments used by most Fortran compilers to pass the lengths of Fortran character arguments, define USE_FC_LEN_T and include Rconfig.h (possibly _via_ R.h) before including R_ext/BLAS.h...

...internals.h. (Neither are part of the API.) PACKAGE INSTALLATION: * Header Rconfig.h contains the value of FC_LEN_T deduced at installation which is used by the prototypes in headers R_ext/BLAS.h and R_ext/Lapack.h but to avoid extensive breakage this is only exposed when USE_FC_LEN_T is defined. If a package's C/C++ calls to BLAS/LAPACK allow for the 'hidden' arguments used by most Fortran compilers to pass the lengths of Fortran character arguments, define USE_FC_LEN_T and include Rconfig.h (possibly _via_ R.h) before including R_ext/BLAS.h...

...internals.h. (Neither are part of the API.) PACKAGE INSTALLATION: * Header Rconfig.h contains the value of FC_LEN_T deduced at installation which is used by the prototypes in headers R_ext/BLAS.h and R_ext/Lapack.h but to avoid extensive breakage this is only exposed when USE_FC_LEN_T is defined. If a package's C/C++ calls to BLAS/LAPACK allow for the 'hidden' arguments used by most Fortran compilers to pass the lengths of Fortran character arguments, define USE_FC_LEN_T and include Rconfig.h (possibly _via_ R.h) before including R_ext/BLAS.h...

...the API.) > > PACKAGE INSTALLATION: > > * Header Rconfig.h contains the value of FC_LEN_T deduced at > installation which is used by the prototypes in headers > R_ext/BLAS.h and R_ext/Lapack.h but to avoid extensive breakage > this is only exposed when USE_FC_LEN_T is defined. > > If a package's C/C++ calls to BLAS/LAPACK allow for the 'hidden' > arguments used by most Fortran compilers to pass the lengths of > Fortran character arguments, define USE_FC_LEN_T and include > Rconfig.h (possibly _via_ R.h) befo...

...f the API.) > > PACKAGE INSTALLATION: > > * Header Rconfig.h contains the value of FC_LEN_T deduced at > installation which is used by the prototypes in headers > R_ext/BLAS.h and R_ext/Lapack.h but to avoid extensive breakage > this is only exposed when USE_FC_LEN_T is defined. > > If a package's C/C++ calls to BLAS/LAPACK allow for the 'hidden' > arguments used by most Fortran compilers to pass the lengths of > Fortran character arguments, define USE_FC_LEN_T and include > Rconfig.h (possibly _via_ R.h) befor...

...ACKAGE INSTALLATION: > > > > * Header Rconfig.h contains the value of FC_LEN_T deduced at > > installation which is used by the prototypes in headers > > R_ext/BLAS.h and R_ext/Lapack.h but to avoid extensive breakage > > this is only exposed when USE_FC_LEN_T is defined. > > > > If a package's C/C++ calls to BLAS/LAPACK allow for the 'hidden' > > arguments used by most Fortran compilers to pass the lengths of > > Fortran character arguments, define USE_FC_LEN_T and include > > Rconfig.h (...

...************************************ >>> Alternatively, do as R does as from version 3.6.1-patched and pass the >>> character length(s) from C to Fortran.? A portable way to do this is >>> ????? // before any R headers, or define in PKG_CPPFLAGS >>> ????? #define USE_FC_LEN_T >>> ????? #include <Rconfig.h> >>> ????? #include <R_ext/BLAS.h> >>> ????? #ifndef FCONE >>> ????? # define FCONE >>> ????? #endif >>> ????? ... >>> ????????????? F77_CALL(dgemm)("N", "T", &nrx, &...

Sorry for cross-posting, but I realized my question might be more appropriate for r-devel... Thank you, Giovanni ________________________________________ From: R-help <r-help-bounces at r-project.org> on behalf of Giovanni Petris <gpetris at uark.edu> Sent: Tuesday, September 10, 2019 16:44 To: r-help at r-project.org Subject: [R] Calling a LAPACK subroutine from R Hello R-helpers!

...C17. (This is consistent with Unix builds.) PACKAGE INSTALLATION: * The default C++ standard has been changed to C++17 where available (which it is on all currently checked platforms): if not C++14 or C++11 is used if available otherwise C++ is not supported. * USE_FC_LEN_T is the default: this uses the correct (compiler-dependent) prototypes for Fortran BLAS/LAPACK routines called from C/C++, and requires adjustment of many such calls - see 'Writing R Extensions' SS6.6.1. * There is initial support for C++23 as several compilers are now...

...C17. (This is consistent with Unix builds.) PACKAGE INSTALLATION: * The default C++ standard has been changed to C++17 where available (which it is on all currently checked platforms): if not C++14 or C++11 is used if available otherwise C++ is not supported. * USE_FC_LEN_T is the default: this uses the correct (compiler-dependent) prototypes for Fortran BLAS/LAPACK routines called from C/C++, and requires adjustment of many such calls - see 'Writing R Extensions' SS6.6.1. * There is initial support for C++23 as several compilers are now...