search for: rtools42

...This GDB was configured as "x86_64_pc-msys". > > (Shouldn't that be msys2?) No. Msys2 is the name for the whole project. "msys" is the name of one of subsystem, one which uses the msys (cygwin) runtime. It is not necessary to understand these details for using Msys2/Rtools42, but if you are still interested to know more, please refer to Msys2 documentation. > If I ignore the messages and try to debug a terminal application, > there are messages > stating that multiple threads are started, and the application accepts > no keyboard > input, and ultimat...

...are started, and the application accepts no keyboard input, and ultimately must be terminated by closing the window. It appears there are other development communities negatively impacted by the fork to mingw-w64. This did not go smoothly. Perhaps it would be safer to simply provide a version of Rtools42 that comes with gdb and msys2? Dominick On Wed, Jan 18, 2023 at 2:40 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > On 1/18/23 04:33, Dominick Samperi wrote: > > Hello, > > > > I tried installing gdb into Rtools42 following the instructions here >...

...igured as "x86_64_pc-msys". > > (Shouldn't that be msys2?) > > No. Msys2 is the name for the whole project. "msys" is the name of one of > subsystem, one which uses the msys (cygwin) runtime. It is not necessary to > understand these details for using Msys2/Rtools42, but if you are still > interested to know more, please refer to Msys2 documentation. > > If I ignore the messages and try to debug a terminal application, there > are messages > stating that multiple threads are started, and the application accepts no > keyboard > input, and u...

...r listers, I have update to rtools43 and, using R 4.2.3 I have been surprised not to be able to compile packages needing compilation when updating. Looks like the path given in gcc? -I"C:/PROGRA~1/R/R-42~1.3/include" -DNDEBUG -DNTIMER -I./SuiteSparse_config -DUSE_FC_LEN_T -I"C:/rtools42/x86_64-w64-mingw32.static.posix/include"???? -O2 -Wall? -std=gnu99 -mfpmath=sse -msse2 -mstackrealign? -c CHMfactor.c -o CHMfactor.o /bin/sh: line 1: gcc: command not found points to rtools42 by defaut I have fixed the issue changing the folder name rtools43 into rtools42, but I wonder wet...

On 1/18/23 04:33, Dominick Samperi wrote: > Hello, > > I tried installing gdb into Rtools42 following the instructions here > https://cran.r-project.org/bin/windows/base/howto-R-4.2.html > > I ran 'pacman -Sy gdb', and the installation seemed to complete without > problems. > > But gdb could not be started because incorrect DLL versions were installed, > in pa...

...ot;. >> >> (Shouldn't that be msys2?) > > No. Msys2 is the name for the whole project. "msys" is the name of > one of subsystem, one which uses the msys (cygwin) runtime. It is > not necessary to understand these details for using > Msys2/Rtools42, but if you are still interested to know more, > please refer to Msys2 documentation. > >> If I ignore the messages and try to debug a terminal application, >> there are messages >> stating that multiple threads are started, and the application >> a...

Hello, I tried installing gdb into Rtools42 following the instructions here https://cran.r-project.org/bin/windows/base/howto-R-4.2.html I ran 'pacman -Sy gdb', and the installation seemed to complete without problems. But gdb could not be started because incorrect DLL versions were installed, in particular, the missing DLL's a...

...so I was wrong to say nothing can happen before main() is called. Strategically placed print statements may be the best strategy. On Wed, Jan 18, 2023 at 8:17 PM Dominick Samperi <djsamperi at gmail.com> wrote: > Since these ?stray threads? were appearing before I installed gdb into > Rtools42, this may be an operating system bug, and not a problem with gdb > or RInside! > > Sent from my iPhone > > On Jan 18, 2023, at 6:08 PM, Dominick Samperi <djsamperi at gmail.com> wrote: > > ? > There may be a more serious problem with gdb, or perhaps a very subtle >...

?s 05:07 de 27/11/2023, Neha gupta escreveu: > Hello, I want to download a package and it gives me the error: > > WARNING: Rtools is required to build R packages, but no version of > Rtools compatible with R 4.2.0 was found. (Only the following > incompatible version(s) of Rtools were found: 4.3.5550) > > Please download and install Rtools 4.2 from >

...RStudio to avoid this extra layer of potential dependencies (but it also does not work if I try within RStudio anyway). I am also not sure how this could be related to the paths: on my personal laptop (on which everything works fine), the only paths related to R are RTOOLS43_HOME (C:/rtools43) and RTOOLS42_HOME (C:/rtools42). The same paths that are currently set on my work laptop. It was not working neither when I tried to add other paths related to R on my work laptop.

? Thu, 31 Aug 2023 11:57:06 +0000 Christophe Bousquet <chr_bousquet at protonmail.com> ?????: > > tools::Rcmd('SHLIB -n hello.c') > > tools::Rcmd('SHLIB hello.c') > > > > What do the commands print? Does the second command fail? > > I basically get no output from the two commands, apart from a new > blank R prompt. So starting a new

On 2/23/24 14:34, avi.e.gross at gmail.com wrote: > This may be a dumb question and the answer may make me feel dumber. > > I have had trouble for years with R packages wanting Rtools on my machine > and not being able to use it. Many packages are fine as binaries are > available. I have loaded Rtools and probably need to change my PATH or > something. I suppose making sure

...b_internal(c('-n', 'hello.c')) or > tools:::.shlib_internal('hello.c'), does it do something useful? I think I tried the commands in the right R session. Here are all the output related to the environment variables for R as well as Sys.which(): ``` > Sys.getenv("RTOOLS42_HOME") [1] "C:/rtools42" > Sys.getenv("RTOOLS43_HOME") [1] "C:/rtools43" > Sys.getenv("R_USER") [1] "C:\\Users\\Christophe Bousquet\\Documents" > Sys.getenv("R_RTOOLS43_PATH") [1] "C:/rtools43/x86_64-w64-mingw32.static.p...

TL:DR there are at least three maybe four ways to address this depending on what you plan to do. I usually adjust PATH to add Rtools using .Rprofile. But if you do that then if you want to use the command line to invoke R then you need to set the PATH separately when you start the shell. For this reason some people like to set it in the User Environment Variables control panel... but some Rtools

...ld with valgrind instrumentation. * libcurl 8.x is now accepted by configure: despite a change in major version number it changes neither API nor ABI. INSTALLATION on WINDOWS: * The makefiles and installer scripts for Windows have been tailored to Rtools43, an update of the Rtools42 toolchain. It is based on gcc 12 and newer versions of MinGW-W64, binutils and libraries. At this time R-devel can still be built using Rtools42 without changes, but when R-devel is installed via the installer, it will by default look for Rtools43. * Old make targets...

...ld with valgrind instrumentation. * libcurl 8.x is now accepted by configure: despite a change in major version number it changes neither API nor ABI. INSTALLATION on WINDOWS: * The makefiles and installer scripts for Windows have been tailored to Rtools43, an update of the Rtools42 toolchain. It is based on gcc 12 and newer versions of MinGW-W64, binutils and libraries. At this time R-devel can still be built using Rtools42 without changes, but when R-devel is installed via the installer, it will by default look for Rtools43. * Old make targets...