-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Segfault from C stack overflow for mips64el and risc64 architectures #619
Comments
Thanks. We don't test Stan on less common archs but maybe @SteveBronder has some idea what we need to change in StanHeaders? |
From the line here
Is this an issue with Boost's BH R package? |
Possibly an issue with Boost. Those Debian packages are using the system boost (which seems to be 1.83) rather than the one in the BH package (which is 1.84) but I doubt that version difference is relevant to |
The command that's failing is Since it's |
Am Wed, Apr 10, 2024 at 07:24:39AM -0700 schrieb Brian Ward:
@tillea - do you know if this is running in `quickjs` or `V8`?
Unfortunately I have no idea. In the log I linked to when opening this issue I find r-cran-v8 is mentioned but only r-cran-quickjsr_1.1.3-1_riscv64.deb is really installed. Maybe that's a hint - but I have no idea about those details.
Hope that helps, Andreas.
|
Patching to install V8 is what I'd try next. RStan should automatically switch over, and hopefully that resolves it. I don't know enough about debian packing to know how to try this myself, but I am able to run that docker file locally so if you can think of a command which I could add to do so, I can try it. |
Indeed, V8 parses complicated Stan programs more reliably than quickjs does, but V8 is more difficult to build for normal users, so rstan depends on quickjs but uses V8 if it happens to be installed. On Debian, or any binary linux repository, V8 should already be packaged by someone. |
I did some manual hacking around inside docker (moved |
Am Wed, Apr 10, 2024 at 08:34:33AM -0700 schrieb Brian Ward:
I did some manual hacking around inside docker (moved `V8` up from `Suggests`, manually ran `apt install r-cran-v8`) and I'm trying to re-run `dpkg-buildpackage` now.
I'll happily add r-cran-v8 to the Build-Depends if this might solve the problem.
Kind regards, Andreas.
|
It is still running, but it has already progressed past the point it was previously failing |
The build using |
Am Wed, Apr 10, 2024 at 12:36:53PM -0700 schrieb Brian Ward:
The build using `r-cran-v8` succeeded
Succeeds in Debian as well. Thanks a lot, Andreas.
|
Am Thu, Apr 11, 2024 at 07:55:34AM -0700 schrieb Brian Ward:
I noticed you are also the debian packager for `r-cran-rstan` -- I would recommend adding `r-cran-v8` to the depends for that package as well, as it would benefit users to have that packaged, as @bgoodri mentions
Just uploaded. Thanks a lot for the hint, Andreas.
|
Summary:
As per Debian bug report rstanarm does not build for mips64el and risc64 architectures.
Description:
As you can see at the end of the build log for mips64el the package fails to build. The relevant part of the log is probably
Reproducible Steps:
I've just got a hint about some dockerfile you could build with
--platform=linux/mips64le
or--platform=linux/risc64
Please note: I have not tested this way to use docker (just copied what others tried with some other package).
RStanARM Version:
2.32.1-1
R Version:
4.3.2
Operating System:
Debian (sid)
The text was updated successfully, but these errors were encountered: