* installing *source* package ‘VIFCP’ ...
** package ‘VIFCP’ successfully unpacked and MD5 sums checked
** using staged installation
** libs
using Fortran compiler: ‘GNU Fortran (GCC) 12.2.0’
using SDK: ‘MacOSX11.3.sdk’
gfortran -arch x86_64  -fPIC  -Wall -g -O2  -c vifcp.f -o vifcp.o
vifcp.f:162:13:

  162 |       pvalue=(-log(-0.5*log(1-siglev))+2.0*log(log(n*1.0))+
      |             1
Warning: Possible change of value in conversion from REAL(8) to REAL(4) at (1) [-Wconversion]
vifcp.f:7:65:

    7 |       double precision y(*),z(10000),v(10000),vtemp,vnew,c(10000)
      |                                                                 1
Warning: Array ‘c’ at (1) is larger than limit set by ‘-fmax-stack-var-size=’, moved from stack to static storage. This makes the procedure unsafe when called recursively, or concurrently from multiple threads. Consider increasing the ‘-fmax-stack-var-size=’ limit (or use ‘-frecursive’, which implies unlimited ‘-fmax-stack-var-size’) - or change the code to use an ALLOCATABLE array. If the variable is never accessed concurrently, this warning can be ignored, and the variable could also be declared with the SAVE attribute. [-Wsurprising]
vifcp.f:7:45:

    7 |       double precision y(*),z(10000),v(10000),vtemp,vnew,c(10000)
      |                                             1
Warning: Array ‘v’ at (1) is larger than limit set by ‘-fmax-stack-var-size=’, moved from stack to static storage. This makes the procedure unsafe when called recursively, or concurrently from multiple threads. Consider increasing the ‘-fmax-stack-var-size=’ limit (or use ‘-frecursive’, which implies unlimited ‘-fmax-stack-var-size’) - or change the code to use an ALLOCATABLE array. If the variable is never accessed concurrently, this warning can be ignored, and the variable could also be declared with the SAVE attribute. [-Wsurprising]
vifcp.f:7:36:

    7 |       double precision y(*),z(10000),v(10000),vtemp,vnew,c(10000)
      |                                    1
Warning: Array ‘z’ at (1) is larger than limit set by ‘-fmax-stack-var-size=’, moved from stack to static storage. This makes the procedure unsafe when called recursively, or concurrently from multiple threads. Consider increasing the ‘-fmax-stack-var-size=’ limit (or use ‘-frecursive’, which implies unlimited ‘-fmax-stack-var-size’) - or change the code to use an ALLOCATABLE array. If the variable is never accessed concurrently, this warning can be ignored, and the variable could also be declared with the SAVE attribute. [-Wsurprising]
vifcp.f:153:72:

  153 |       sta=cw(1)
      |                                                                        ^
Warning: ‘MEM[(real(kind=8)[0:D.4280] *)_90][0]’ may be used uninitialized [-Wmaybe-uninitialized]
vifcp.f:153:72: Warning: ‘MEM[(real(kind=8)[0:D.4280] *)_90][0]’ may be used uninitialized [-Wmaybe-uninitialized]
clang -arch x86_64 -dynamiclib -Wl,-headerpad_max_install_names -undefined dynamic_lookup -single_module -multiply_defined suppress -L/Library/Frameworks/R.framework/Resources/lib -L/opt/R/x86_64/lib -o VIFCP.so vifcp.o -L/opt/gfortran/lib/gcc/x86_64-apple-darwin20.0/12.2.0 -L/opt/gfortran/lib -lgfortran -lquadmath -F/Library/Frameworks/R.framework/.. -framework R -Wl,-framework -Wl,CoreFoundation
installing to /Volumes/Builds/packages/big-sur-x86_64/results/4.3/VIFCP.Rcheck/00LOCK-VIFCP/00new/VIFCP/libs
** generating debug symbols (dSYM)
** R
** byte-compile and prepare package for lazy loading
** help
*** installing help indices
** building package indices
** testing if installed package can be loaded from temporary location
** checking absolute paths in shared objects and dynamic libraries
** testing if installed package can be loaded from final location
** testing if installed package keeps a record of temporary installation path
* DONE (VIFCP)