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
[BUG] Torsten installation issue #35
Comments
Can you go to Torsten/cmdstan and do make build and let me know the output? Thanks. |
Here's what I entered into the cmd terminal (and the results). And note that I've removed the
|
I've just pushed a fix, please
Perhaps you can try again using "mingw32-make |
Thank you. I re-cloned your It does seem there's something off with my make. I do have Rtools40 installed, which I verified with:
I had previously also put both g++ and make on the PATH, per the cmdstan-installation guide you linked above. Here's a screenshot (see Rtools1 and Rtools2): Furthermore, in R, I checked the PATH, which also confirms the presence of Rtools40 (I truncated the output here):
mingw32-make in R:
and g++ in R
And note that cmdstan by itself (i.e. not the Torsten version) compiles models properly, so I'm assuming that to a certain degree I have a functional make . . . but something is clearly still off and I'm uncertain how to proceed . . . |
what's the output of |
Okay, I'm not sure this is exactly what you're looking for, but I tried both
|
Sorry for being terse. What's the output of cd C:\Programs\Git\Torsten\cmdstan
mingw32-make.exe ..\example-models\pk2cpt\pk2cpt.exe ? |
ah okay, got it, thank you for the clarification! once I
|
This helps, thanks. Now please try pacman -Sy mingw-w64-x86_64-make --noconfirm to install mingw32-make. You'll need to ensure the newly installed mingw32-make is in your PATH. |
hmm here's what happened in the Windows 10 cmd prompt:
I also tried in Cygwin64, but it too didn't like Would mingw64 from this site work? If so, in addition to making sure it is in my PATH, should mingw64 be placed anywhere in particular (i.e., does it need to be within Thank you for all your help!! |
I don't know. But you can check the previous discussion here on how to setup mingw32-make: https://discourse.mc-stan.org/t/cmdstanr-with-rtools-4-0-on-windows-10-mingw32-make-exe-missing/14791 |
Thanks for that link, @yizhang-yiz. I followed the directions, opened the rtools bash, and ran the following:
and again in the rtools bash, I ran:
and per the attached photo on my second post on this thread, I have the following on the PATH:
as stated in the instructions here and here. the only difference I can see between my PATH and the instructions is that, for whatever reason, I don't have an I apologize for continuing to put my difficulty here. I know we seem to have wandered from the Torsten install. I simply don't understand how I can successfully use |
Then you should have where mingw32-make.exe and let me know the output. If you do find cd C:\Programs\Git\Torsten\cmdstan
C:\Programs\rtools40\mingw64\bin\mingw32-make.exe ..\example-models\pk2cpt\pk2cpt.exe |
yup, as best as I can tell, However (and once again in the rtools bash):
and
BUT, once I navigated into the exact file where I can see that
|
Could you |
Yesterday I deleted the Torsten repo and re-cloned from the develop branch (as I saw that that where was you'd recently pushed). I'm using GitHub Desktop (sorry, ecologist here trying to use developer tools . . . ), and on the Torsten Master branch just now I indeed was able to pull an update. Re-running (again, in rtools bash) an attempt at compiling a Torsten model produced a slightly new flavor of error:
|
This is odd. Could you do C:/Programs/rtools40/mingw64/bin/mingw32-make.exe build ? |
sure thing. it makes me feel a little better that this is an odd issue, and not something blatantly obvious! first, from a new rtools bash:
and then once I
|
You need to do it at Torsten/cmdstan: cd C:\Programs\Git\Torsten\cmdstan
C:\Programs\rtools40\mingw64\bin\mingw32-make.exe build |
Ah okay, thank you. And since I updated Torsten, I re-checked the
and now per your most recent post:
|
That means you don't have g++ in your PATH and why I find it odd as clearly your PATH contains CXX=C:/Programs/rtools40/mingw64/bin/g++.exe
CC=C:/Programs/rtools40/mingw64/bin/g++.exe But first, please double check |
Yes, I do believe g++. exe is right where it is supposed to be: and just to confirm re: a new file (definitely preferable over restarting Windows!). I don't have a Thank you again for all of your help!! |
Do cd C:\Programs\Git\Torsten\cmdstan\make
touch local then use wordpad to open |
ahhh okay. thank you! done. I reran:
and also tried to compile a Torsten model, and got the same error from both:
I'm not familiar with missing separators, but I'm starting to read online. I tried both:
and
which both produced the same error as above (and I'll confess I don't actually know what I'm doing here). |
Just want to log the diagnostics done with @zhrandell offline before closing. The issue of downloading of the latest stanc.exe has been fixed here. The issue of building binaries was caused by Windows |
Hello,
I'm keen to utilize the event schedule functionality of Torsten, and I've encountered an installation issue.
my information:
Windows 10;
R version 4.0.4;
rstan version 2.21.2;
cmdstan version 2.27.0;
I am able to compile models via cmdstan using code from this page.
I next cloned the Torsten repo, and set the cmdstan path to the version of cmdstan within the cloned Torsten repo (per the directions on your installation page):
Next I tried to compile example models from the Torsten repo (via code from the Installation page):
which produced the following error:
After examining the error and after reading posts online, I realized Torsten's version of cmdstan did not contain a stanc.exe file . . . specifically, there was no
stanc.exe
file inTorsten/cmdstan/bin
.So, in a fit of improvisation, I copied the stanc.exe file from the "standard" cmdstan into Torsten's cmdstan
(which may be highly inappropriate -- I apologize -- I'm at the very edge of my competence here).
Running the above model then returned:
I'm assuming my copying of the
stanc.exe
file somewhat patched one issue, but created another? Or is there an underlying issue with my Make? I'm assuming since cmdstan works properly, my g++ and Make toolchain are in place?I very much appreciate any assistance here!!
The text was updated successfully, but these errors were encountered: