-
-
Notifications
You must be signed in to change notification settings - Fork 262
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
Does not build on 32 bit architectures any more #1032
Comments
According to the log, it's running four parallel build jobs. Is it possible to reduce that in the autobuilders? That would be the easiest way to reduce the amount of memory needed |
I tried to sneak in the option --no-parallel into the Debian Build process on my local system where I'm using an i386 chroot for test builds. It says:
Kind regards and thanks a lot for your quick response, Andreas. |
Any further ideas? Otherwise I'd restrict the build to 64bit architectures. |
Sorry about the delay, I'll be able to test this locally today and will see what a fix could be |
I'm running into a similar issue with the 32-bit build of rstan 2.21.8 on Windows R 4.1 and below, and CRAN is as well: https://www.r-project.org/nosvn/R.check/r-oldrel-windows-ix86+x86_64/rstan-00install.html. The error is always
It looks like rstan is now bumping against the 2/4 GB memory limit with 32-bit platforms (at least on Windows). Successful workarounds I've tried so far are to:
editbin /LARGEADDRESSAWARE "C:\rtools40\mingw32\lib\gcc\i686-w64-mingw32\8.3.0\cc1plus.exe" I got rstan to build for 32-bit after this, but it feels like a sketchier workaround. Perhaps the older Rtools could get cc1plus.exe built with the large address aware flag, but I'm not sure how feasible that is. |
The culprit here is the @bgoodri thoughts? |
It will probably still build on 32bit machines if you can add -flto to the
compiler flags to utilize Link Time Optimization. That should keep the
intermediate files below the address space limit.
|
The Debian autobuilders matrix shows failures for |
I tried this but failed (and my mail about this did not make it here to the issue tracker unfortunately). |
Well, the arch name is |
If bookworm is going to use a version of Boost that is less than the BH 1.81 which is on CRAN, then you could get the previous version of r-cran-rstan under the freeze. In the version of rstan on CRAN, I just changed the compilation to deal with linker errors induced by Boost 1.81, but that apparently induced different errors on 32bit architectures. |
@bgoodri If you refer to CRAN version of P. S. Noticed that I used UPD. Yes, |
So I think part of the solution of this issue should be
Kind regards, Andreas. |
Summary:
The 32bit autobuilders of the Debian package all failed to build version 2.21.8 while these succeeded for version 2.21.7.
Description:
There is a full build log for i386 which ends with
Reproducible Steps:
Please try to build in i386 (or armel/armhf).
RStan Version:
2.21.8
R Version:
4.2.2.20221110
Operating System:
Debian unstable
Kind regards, Andreas.
The text was updated successfully, but these errors were encountered: