* installing *source* package ‘fields’ ... ** using staged installation ** libs using C compiler: ‘gcc-14 (Debian 14.2.0-3) 14.2.0’ using Fortran compiler: ‘GNU Fortran (Debian 14.2.0-3) 14.2.0’ gcc-14 -I"/home/hornik/tmp/R-d-gcc-14/include" -DNDEBUG -I/usr/local/include -DUSE_TYPE_CHECKING_STRICT -D_FORTIFY_SOURCE=3 -DSTRICT_R_HEADERS=1 -fpic -g -O2 -Wall -Wstrict-prototypes -pedantic -mtune=native -c ExponentialUpperC.c -o ExponentialUpperC.o gcc-14 -I"/home/hornik/tmp/R-d-gcc-14/include" -DNDEBUG -I/usr/local/include -DUSE_TYPE_CHECKING_STRICT -D_FORTIFY_SOURCE=3 -DSTRICT_R_HEADERS=1 -fpic -g -O2 -Wall -Wstrict-prototypes -pedantic -mtune=native -c RdistEarth.c -o RdistEarth.o gcc-14 -I"/home/hornik/tmp/R-d-gcc-14/include" -DNDEBUG -I/usr/local/include -DUSE_TYPE_CHECKING_STRICT -D_FORTIFY_SOURCE=3 -DSTRICT_R_HEADERS=1 -fpic -g -O2 -Wall -Wstrict-prototypes -pedantic -mtune=native -c addToDiagC.c -o addToDiagC.o gcc-14 -I"/home/hornik/tmp/R-d-gcc-14/include" -DNDEBUG -I/usr/local/include -DUSE_TYPE_CHECKING_STRICT -D_FORTIFY_SOURCE=3 -DSTRICT_R_HEADERS=1 -fpic -g -O2 -Wall -Wstrict-prototypes -pedantic -mtune=native -c compactToMatC.c -o compactToMatC.o gcc-14 -I"/home/hornik/tmp/R-d-gcc-14/include" -DNDEBUG -I/usr/local/include -DUSE_TYPE_CHECKING_STRICT -D_FORTIFY_SOURCE=3 -DSTRICT_R_HEADERS=1 -fpic -g -O2 -Wall -Wstrict-prototypes -pedantic -mtune=native -c expfnC.c -o expfnC.o gfortran-14 -fpic -g -O2 -Wall -mtune=native -c fieldsF77Code.f -o fieldsF77Code.o fieldsF77Code.f:104:32: 104 | double precision A(NMAX,4),V(NMAX,7) | 1 Warning: Array ‘a’ 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] fieldsF77Code.f:108:23: 108 | integer idx(NMAX) | 1 Warning: Array ‘idx’ 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] fieldsF77Code.f:107:23: 107 | integer imx(NMAX) | 1 Warning: Array ‘imx’ 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] fieldsF77Code.f:106:59: 106 | double precision ux(NMAX),uy(NMAX), uw(NMAX),ud(NMAX),utr | 1 Warning: Array ‘ud’ 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] fieldsF77Code.f:106:50: 106 | double precision ux(NMAX),uy(NMAX), uw(NMAX),ud(NMAX),utr | 1 Warning: Array ‘uw’ 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] fieldsF77Code.f:106:31: 106 | double precision ux(NMAX),uy(NMAX), uw(NMAX),ud(NMAX),utr | 1 Warning: Array ‘ux’ 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] fieldsF77Code.f:106:40: 106 | double precision ux(NMAX),uy(NMAX), uw(NMAX),ud(NMAX),utr | 1 Warning: Array ‘uy’ 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] fieldsF77Code.f:104:42: 104 | double precision A(NMAX,4),V(NMAX,7) | 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] fieldsF77Code.f:379:43: 379 | double precision work(nobs),diag(mxM),dumm1(1),dumm2(1) | 1 Warning: Array ‘diag’ 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] gcc-14 -I"/home/hornik/tmp/R-d-gcc-14/include" -DNDEBUG -I/usr/local/include -DUSE_TYPE_CHECKING_STRICT -D_FORTIFY_SOURCE=3 -DSTRICT_R_HEADERS=1 -fpic -g -O2 -Wall -Wstrict-prototypes -pedantic -mtune=native -c init.c -o init.o gcc-14 -I"/home/hornik/tmp/R-d-gcc-14/include" -DNDEBUG -I/usr/local/include -DUSE_TYPE_CHECKING_STRICT -D_FORTIFY_SOURCE=3 -DSTRICT_R_HEADERS=1 -fpic -g -O2 -Wall -Wstrict-prototypes -pedantic -mtune=native -c multebC.c -o multebC.o gcc-14 -I"/home/hornik/tmp/R-d-gcc-14/include" -DNDEBUG -I/usr/local/include -DUSE_TYPE_CHECKING_STRICT -D_FORTIFY_SOURCE=3 -DSTRICT_R_HEADERS=1 -fpic -g -O2 -Wall -Wstrict-prototypes -pedantic -mtune=native -c rdistC.c -o rdistC.o gcc-14 -shared -L/home/hornik/tmp/R-d-gcc-14/lib -Wl,-O1 -o fields.so ExponentialUpperC.o RdistEarth.o addToDiagC.o compactToMatC.o expfnC.o fieldsF77Code.o init.o multebC.o rdistC.o -lgfortran -lm -lquadmath -L/home/hornik/tmp/R-d-gcc-14/lib -lR installing to /home/hornik/tmp/CRAN_recheck/fields.Rcheck/00LOCK-fields/00new/fields/libs ** R ** data ** inst ** 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 (fields)