Daniel, note that you can choose R-devel in MacBuilder (select "development" under R version). If your package works on the MacBuilder then it's good as far as macOS goes since that is identical to the CRAN setup.
Cheers, Simon > On Dec 14, 2022, at 12:02 AM, Wollschlaeger, Daniel > <wollschlae...@uni-mainz.de> wrote: > > (This is a re-post from R-pkg-devel hoping to get more feedback) > > A package of mine was recently archived from CRAN because one of its > examples results in a crash on the M1mac platform: > https://www.stats.ox.ac.uk/pub/bdr/M1mac/MeshAgreement.out > > As I don't have access to a Mac, I'm very grateful for Macbuilder. However, > there, the package tests without errors (link likely to stop working): > https://mac.r-project.org/macbuilder/results/1670186023-a7f313b721c2b516/ > > One difference I noticed between the Macbuilder and CRAN systems is that > Macbuilder builds for aarch64-apple-darwin20 (64-bit), whereas CRAN builds > for aarch64-apple-darwin22.1.0 (64-bit). Moreover, Macbuilder uses R-4.2.1 > whereas CRAN uses R-devel r83383. > > The example leading to the crash uses a function from the imported package > cgalMeshes which relies on compiled code. cgalMeshes itself is on CRAN and > apparently tests without errors on M1mac. I would like to investigate > further how to prevent the crash, but it may depend on the MacOS version, or > on the R version. Are there publicly available options to test packages on a > system that is very similar to the CRAN M1mac in order to implement the > necessary changes to get the package back on CRAN? > > Many thanks in advance > > Daniel > > _______________________________________________ > R-SIG-Mac mailing list > R-SIG-Mac@r-project.org > https://stat.ethz.ch/mailman/listinfo/r-sig-mac _______________________________________________ R-SIG-Mac mailing list R-SIG-Mac@r-project.org https://stat.ethz.ch/mailman/listinfo/r-sig-mac
