Hi.
I have asked to correct a simple (apparently) update of my mnormt package, see
https://cran.r-project.org/web/packages/mnormt/index.html
The request was to amend a few Rd files and the DESCRIPTION, and this was the
easy part. Unfortunately, after I rebuilt the package and run
R CMD check --as-cran --run-donttest mnormt_2.1.2.tar.gz
unexpected problems appeared. The 00check.log file is as follows:
* using log directory ‘/Users/aa/SW-aa/Pkg-mnormt/mnormt.Rcheck’
* using R version 4.5.2 (2025-10-31)
* using platform: aarch64-apple-darwin20
* R was compiled by
Apple clang version 16.0.0 (clang-1600.0.26.6)
GNU Fortran (GCC) 14.2.0
* running under: macOS Tahoe 26.2
* using session charset: UTF-8
* using options ‘--run-donttest --as-cran’
* checking for file ‘mnormt/DESCRIPTION’ ... OK
* this is package ‘mnormt’ version ‘2.1.2’
* package encoding: UTF-8
* checking CRAN incoming feasibility ... OK
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for executable files ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking serialization versions ... OK
* checking whether package ‘mnormt’ can be installed ... ERROR
Installation failed.
See ‘/Users/aa/SW-aa/Pkg-mnormt/mnormt.Rcheck/00install.out’ for details.
* DONE
Status: 1 ERROR
Since the 00install.out file is quite long, it has been placed at
http://azzalini.stat.unipd.it/SW/00install.out
It shows a long list of Fortran warning messages, many of them of the following
form:
Warning: Possible change of value in conversion from REAL(8) to INTEGER(4) at
(1) [-Wconversion]
and finally
ld: library 'emutls_w' not found
clang: error: linker command failed with exit code 1 (use -v to see invocation)
where the process has stopped.
This bunch of warnings/error surprised me, since that Fortran code has been in
use for several years and various versions of the package, without showing
these problems.
Since my macOS has recently been updated to version 26.2 (Tahoe) with a
corresponding update of Xcode, I wonder whether this update has anything to do
with these problems.
Any suggestions are much appreciated!
Best regards,
Adelchi Azzalini
http://azzalini.stat.unipd.it
______________________________________________
[email protected] mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
