-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Problems with compiling mixutre models on Windows (rstantools 2.3.0) #107
Comments
Your version of
The latest 2.26.x version is 2.26.17. Can you try updating and then try your compilation again? |
Will do! Though I might misunderstand how |
Note that when you run |
That makes sense, though I ran |
I am working on submitting a new release of an R package that uses rstan to CRAN, but rstantools 2.3.0 seems to have caused problems compiling some of the package's Stan models on Windows machines. In particular, it seems like any model containing
log_mix(...)
leads to a problem. I was able to build the package withpkgbuild::compile_dll()
and rstantools 2.3.0 on a Mac and Linux OS, but not on my Windows machine (Windows 11 version 21H2; R version 4.2.1; rstan version 2.26.13; Rcpp 1.0.9; rstantools 2.2.0; and Rtools 4.2). Below is a screenshot of the output of.Last.error
that arises when runningpkgbuild::compile_dll()
inside the package's root directory.Running
devtools::check_win_release()
on the Mac system I was able to successfully build the package on yields the same error. I also tested building a new R package using rstan from scratch on my Windows machine following the instructions here, which worked until I added a Stan model toinst\stan
containing a call tolog_mix(...)
. In particular, I tried adding the stan models namedMCMC.stan
andMutrate_est2.stan
in my package'sinst/stan
directory. Adding the stan model namedHybrid.stan
, which does not contain a call tolog_mix()
but is otherwise identical to theMCMC.stan
model did not yield any problems when building the test package withpkgbuild::compile_dll
.The text was updated successfully, but these errors were encountered: