Closed vandenman closed 2 days ago
That's strange. We implement the CRAN-recommended workaround here:
https://github.com/statnet/ergm/blob/dfbce58cffb38ccafc735798589a0fbdd1fcf2c2/src/etamap.c#L38-L46
That makes sense, but I'm not sure if this workaround is sufficient to avoid the issue. As far as I know, R/ CRAN assumes that packages within patch versions of R are binary compatible. So if you use R-4.4.0 on Windows or macOS and install ergm
, then R downloads a binary made with R-4.4.2, effectively bypassing the ifdef. In my case on Linux, renv
linked a version of ergm
build with R-4.4.2 and then I also got the error.
CRAN probably should not have added that function to the API during a minor release. Ultimately, I don't think this is something that can be fixed on my end.
The current minimum R version is 4.1, as specified in https://github.com/statnet/ergm/blob/dfbce58cffb38ccafc735798589a0fbdd1fcf2c2/DESCRIPTION#L23
However, when installing the current CRAN version on say, R-4.4.0 I see this error:
The C function
Rf_allocLang
was introduced in R-4.4.1, see https://developer.r-project.org/blosxom.cgi/R-devel/NEWS/2024/06/05#n2024-06-05Perhaps this should also be caught by R CMD CHECK somehow, but that is a different bug report I guess :sweat_smile: