r-cran-rstan issue and r-cran-boost version [notifications@github.com: Re: [stan-dev/rstan] Does not build on 32 bit architectures any more (Issue #1032)]
On 8 March 2023 at 08:18, Andreas Tille wrote:
| Hi Dirk,
|
| upstream suspects that the issue to build r-cran-rstan might be connected to
| the boost version that is used.
As you may know, I am upstream for BH 1.81.0-1. It reached CRAN after a month
of careful alignment with reverse depende on Jan 22. That is six weeks ago.
I cannot do anything about you deciding not to update it sooner, sorry.
Also FYI new issue between clang16, Boost and the stan complex -- but as it
is clang-only (and brand-new clang as CRAN sometimes does for forward-looking
tests) it may not affect us:
https://github.com/eddelbuettel/bh/issues/92
Dirk
| Its to late to change anything for bookworm but having r-cran-bh 1.81 in
| experimental could help clarifying the issue with r-cran-rstan.
|
| Kind regards
| Andreas.
|
| ----- Weitergeleitete Nachricht von bgoodri <notifications@github.com> -----
|
| Date: Tue, 07 Mar 2023 10:58:37 -0800
| From: bgoodri <notifications@github.com>
| To: stan-dev/rstan <rstan@noreply.github.com>
| Cc: Andreas Tille <tille@debian.org>, Mention <mention@noreply.github.com>
| Subject: Re: [stan-dev/rstan] Does not build on 32 bit architectures any more (Issue #1032)
|
| 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.
|
| --
| Reply to this email directly or view it on GitHub:
| https://github.com/stan-dev/rstan/issues/1032#issuecomment-1458671266
| You are receiving this because you were mentioned.
|
| Message ID: <stan-dev/rstan/issues/1032/1458671266@github.com>
|
| ----- Ende weitergeleitete Nachricht -----
|
| --
| http://fam-tille.de
--
dirk.eddelbuettel.com | @eddelbuettel | edd@debian.org
Reply to: