stan-dev / stan-dev/rstan

RStan installation failure, status 65535, cannot open file 'file7001d882ea.cpp.err.txt'

Open
#546 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
R
Stars
1.1k
Forks
266
Avg merge
2h 56m
Merged PRs (30d)
1

Description

Hellow
I am trying to use Rstan.
I followed the instructions from this page:

https://github.com/stan-dev/rstan/wiki/Installing-RStan-on-Windows

Under the section "Verify that Rtools can be used in R"

fx <- inline::cxxfunction( signature(x = "integer", y = "numeric" ) , '

  • return ScalarReal( INTEGER(x)[0] * REAL(y)[0] ) ;
  •                        ' )
    

#I get this result

Error in file(con, "r") : cannot open the connection
In addition: Warning messages:
1: In system(cmd, intern = !verbose) :
running command 'C:/PROGRA1/R/R-351.1/bin/x64/R CMD SHLIB file7001d882ea.cpp 2> file7001d882ea.cpp.err.txt' had status 65535
2: In file(con, "r") :
cannot open file 'file7001d882ea.cpp.err.txt': No such file or directory

the file name mentioned: 'file7001d882ea.cpp.err.txt' changes every time I try the same function again. but the status 65535 remains.

I am using the following:
R Version: 3.5.1
RStan Version: 2.17.3
Rtools: Rtools34.exe "Frozen"
OS: Windows 8

I spend a lot of time trying to solve that but I can not. I am grateful for any help.
thank you !

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked RStan Windows installation instructions and reproduce the inline::cxxfunction example using R 3.5.1, RStan 2.17.3, Rtools34, and Windows 8. Inspect the R CMD SHLIB invocation and whether its generated .err.txt file is created. Done means identifying a confirmed compatibility or configuration cause and documenting an actionable resolution.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.