Replies: 18 comments
-
Can you compile anything? Or just |
Beta Was this translation helpful? Give feedback.
-
I have a few models to compile, m23 is the frist one. I tried skipping m23 as a test but the others have the same error. |
Beta Was this translation helpful? Give feedback.
-
Ok; I'd look at the Rtools40 installation; were you able to install a package from source? See the example below: |
Beta Was this translation helpful? Give feedback.
-
Yes, I followed the examples below from the rtools site and no problem installing from the source. |
Beta Was this translation helpful? Give feedback.
-
Sounds good. Happy to keep working with you on this. Let me know if there are any other leads to investigate. |
Beta Was this translation helpful? Give feedback.
-
Thanks Kyle. Since that's the only error message I got, I'm not sure what else I can look into at this point. |
Beta Was this translation helpful? Give feedback.
-
You could share more information:
Etc ... there must be more information that could be shared that might suggest what is happening on your system. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
@tmscs Any luck with any of this? |
Beta Was this translation helpful? Give feedback.
-
Thanks for the tips Kyle. Apology for my delayed response. I've now managed to test your suggestions as below. what does the output look like when you compiled the package from source?This is the output when I installed the testing json package on the rtool40 website:
can you debug mread and let us know at what point you get the error (?debugonce)?The is the output when I tried
did you blow away everything from your R 3.x install? Could your system be looking at / for old files?I think so. what is the sessionInfo()?I've checked this before and couldn't detect any irregularities:
what do you get with pkgbuild::check_build_tools()?
Is this a network drive?No. Are you working with a network drive at all?No. Are there spaces in the path to R?Only the space in Programe Files as here: "C:\Program Files\R\R-4.0.2\bin\x64" Does this work: tmp <- tempfile(); cat(letters,file = tmp); readLines(tmp) (can you write to tempdir())?'This is the output. The accent in my name is the one causing the encoding problem in the path below. I've been using mrgsolve on this computer with earlier verions of R before so not sure if it indicates any problem:
This: pkgbuild::check_compiler(debug = TRUE)?This is the output:
|
Beta Was this translation helpful? Give feedback.
-
I've been using another machine for now while trying to solve this. I've checked through the outputs above for quite a few times now and the output from |
Beta Was this translation helpful? Give feedback.
-
Thanks, @tmscs ; I'm sorry I missed your output from 2 weeks ago; I'll look at it this morning after a couple of meetings and get back to you. It does look like most of the stuff is in place and working. |
Beta Was this translation helpful? Give feedback.
-
I wonder if this is the culprit: Can you try this: then mod <- mcode_cache("m23", s23code, project = "C:/project") I'd like to know what happens there. Additionally: Create a directory: then mod <- mcode_cache("m23", s23code, project = "C:/project", soloc = "C:/build") |
Beta Was this translation helpful? Give feedback.
-
mod <- mcode_cache("m23", s23code, project = enc2native(tempdir())) tmp <- enc2native(tempdir())
mod <- mcode_cache("m23", s23code, project = tmp, soloc = tmp) |
Beta Was this translation helpful? Give feedback.
-
Thanks so much Kyle, it works now! The minimum change for things to work is by specifying "soloc":
With the above, it works even without specifying the project folder. It did not work when I only specified the project folder without "soloc". So it looks like "soloc" here is the issue. This latter code here also did not work with the same error:
May I ask if you know what is the reason for this error, so I can avoid this in the future? |
Beta Was this translation helpful? Give feedback.
-
Thanks for finding the minimal change. That's really helpful.
When you use So I wondered if this was some problem with the path to tempdir() but it looks like that isn't it (since I guess it could be some permissions issue, but all of those directories for Short term fixJust keep using this. You can put the following options(mrgsolve.soloc = "C:/build") at the top of your script or in But obviously I'd like to figure out why this is happening and fix the root cause so you don't always have to do this. I can throw out some ideas but I'm afraid it will be tedious. Would you be willing to so a screen share some time and try some things together? I think we could make a lot of ground pretty quick. If you'd be ok with that, could you email me at the address in my github profile? Thanks, |
Beta Was this translation helpful? Give feedback.
-
Yes, we can look into this when you have a moment. Feel free to let me know how I can help. |
Beta Was this translation helpful? Give feedback.
-
I've been using mrgsolve for a while now. I've recently updated R to v4.0.2 with rtools40 and the latest mrgsolve on CRAN, and started seeing this error when compiling with this code that ran without any problems before that update. Does anyone know what's wrong?
Beta Was this translation helpful? Give feedback.
All reactions