nealrichardson commented on issue #43317: URL: https://github.com/apache/arrow/issues/43317#issuecomment-2261788123
You could wait to see if Uwe waves it through, or you could reply and explain that these are ifdef'd for backwards compatibility only. The in-case-of-emergency hack would be to sed out these references from the .cpp files in the `configure` script if R is > 4.4 (the checks are only on devel now, right?). But it seems like this is a more general problem CRAN will have to solve, if they're adding new "official" API functions to replace some of these things but they're only in R-devel, how can you be on CRAN if you depend on them? What's surprising to me is that, at least by the internal function names `check` is calling, they're looking at the compiled object files, which I would expect not to have these symbols in them because of the `#ifdef`: https://github.com/wch/r-source/blob/032b8240be6c8cf5e8e85ecde6f3f23e46739716/src/library/tools/R/sotools.R#L721-L768 And that function is wrapping `nm`. In fact, I do see these symbols showing up locally, on new enough R, for example: ``` npr@nealrichardson-3P29 r % nm src/arrow.so | grep Rf_findVarInFrame3 U _Rf_findVarInFrame3 ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
