You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have seen a few issues from users that turned out to be muliple g++ installed on the system. Typically some MinGw install or something along those lines.
What we could do is try to prepend the path to rtools on the front of PATH (like we do for TBB) which would then force the use of the right compiler.
We would check the usual paths to rtools and if found use it. If the user installed it in some non-typical location, then we would not prepend it.
The text was updated successfully, but these errors were encountered:
Not sure whether is what you're talking about, but for Windows there's an RTOOLS40_HOME environment variable that gives the install directory for Rtools (I believe the equivalent for version 3.5 and lower is RTOOLS_HOME), which could simplify finding the right compiler
Good call. RTOOLS40_HOME is definitely something we could rely on. We do have to double-check if this gets set for all RTools 4.0 installs. Hopefully, there is no way of not setting it. If that is the case, then it should be easy for R 4.0.
We have seen a few issues from users that turned out to be muliple g++ installed on the system. Typically some MinGw install or something along those lines.
What we could do is try to prepend the path to rtools on the front of PATH (like we do for TBB) which would then force the use of the right compiler.
We would check the usual paths to rtools and if found use it. If the user installed it in some non-typical location, then we would not prepend it.
The text was updated successfully, but these errors were encountered: