-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set Biarch: true
for old R versions on Windows
#1017
Conversation
06fac06
to
9202386
Compare
I'm slightly tempted to leave this for a bit to see if anyone complains about it. |
Me and my Windows 3.6 tidyr builds will complain loudly 🤣 More seriously I imagine there are some corporate businesses stuck on older versions of R that are also stuck on 32-bit R that might come out and complain. I remember 32 bit R was needed to connect to an Access database (all too common) |
CRAN checks of packages that use {purrr} also complain. And CI/CD for those. |
Hi, I think this is related with a bunch of errors on CRAN:
A quick search on GitHub: https://github.com/search?q=%22DLL+purrr+not+found%3A+maybe+not+installed+for+this+architecture%3F%22&type=issues |
We will submit a patch to CRAN in early January when we are all back at work. |
Now that we have a
configure.win
script, we are forced to also setBiarch: true
so that when purrr is installed from source on R < 4.2, it installs for both 32 and 64 bit Windows.Otherwise, we get failures like this one in tidyr on our Windows 3.6 builds if we request
purrr (>= 1.0.0)
:https://github.com/tidyverse/tidyr/actions/runs/3743952288/jobs/6356732834
This doesn't happen on newer versions of R because R 4.2 dropped support for 32 bit Windows. This is why windows-latest passes on tidyr.
See 6.3.4 of https://cran.r-project.org/doc/manuals/r-patched/R-admin.html for more details.
This might be important enough for a patch purrr release.