R 4.3.0 not working as expected on macOS

[glatterf42]

Context

Our nightly CI checks recently failed for all macOS runs. Upon closer inspection (the details of which can be found on Slack, this was related to the interplay of the macOS image, Jupyter, Reticulate, and the Java backend of ixmp. The current version of the macOS image installs version 4.2.3 of R, while the r-lib/actions/setup-r@v2 GitHub Action installs the newest version, which recently became 4.3.0. In theory, this should uninstall the earlier version and keep 4.3.0, but it is possible that process was not completed and there remained some interference of the two version. It is, however, also possible that the R version 4.3.0 does not work for ixmp on macOS (at least on this specific version), which is why we create this issue. Users experiencing related issues are encouraged to record their specific experiences here so that we can work on a fix should that be necessary.

PR #478 fixes this issue for the CI tests by pinning version 4.2.3 of R in the workflow file (i.e., the one currently used in the macOS image linked above). An alternative, maybe more sustainable solution, on our side would include finding where the CRAN R version 4.3.0 installs the library libgcc_s.1.dylib and making sure that either

• this location is included in the search path of ixmp or
• the install location is changed to some path that is searched by ixmp

On the user side for a quick fix, please try using version 4.2.3 of R specifically.

Versions

Output of ixmp show-versions

``` ```

[RahJa24]

Hello,

I am facing a few problems while running the Austria.ipynb. I believe the problem is with the dylib files, as they have been written for AMD structures and I am currently using Apple Silicion ARM, M1 structure. is there anyway to work around this? Basiclaly are there any dylib file translators that I can use to generate dylib files that can be used for ARM structures? Please help! I am stuck on this for days now!

[khaeru]

@RahJa24 —you don't give enough information to be sure, but it sounds like your issue is not related to this one on which you've commented.

Can you please:

• Check existing issues (perhaps #473) to (a) see whether the symptoms match yours precisely and (b) if they are already resolved, if the solution works for you?
• If there are none, open a new issue with a complete description. That would specific output or problem description (not merely "a few problems"); version(s) of ixmp and other packages you are using; actions to reproduce the issue; etc.