search for: chr_bousquet

Displaying 7 results from an estimated 7 matches for "chr_bousquet".

2023 Aug 30
1
Problems with installing R packages from source and running C++ in R, even on fresh R installation
On Wed, 30 Aug 2023 16:31:20 +0000 Christophe Bousquet <chr_bousquet at protonmail.com> wrote: > So, yes, it seems possible for R to localize paths related to > Rtools... But then, I really do not get where things go wrong... When installing packages containing code to compile, R eventually calls R CMD SHLIB. Same thing happens with inline C++: it gets s...
2023 Aug 31
1
Problems with installing R packages from source and running C++ in R, even on fresh R installation
> When installing packages containing code to compile, R eventually calls > R CMD SHLIB. Same thing happens with inline C++: it gets stored in a > temporary file, compiled into a *.dll using R CMD SHLIB and then loaded > using dyn.load(). > > Write the following into a file named hello.c: > > #include <R.h> > #include <Rinternals.h> > SEXP hello(void) {
2023 Aug 31
1
Problems with installing R packages from source and running C++ in R, even on fresh R installation
? Thu, 31 Aug 2023 14:01:54 +0000 Christophe Bousquet <chr_bousquet at protonmail.com> ?????: > So when I run the commands, I get this output. I honestly have no > clue whether this can be considered as something useful or not :-/ > > ``` > > tools:::.shlib_internal(c('-n', 'hello.c')) > make cmd is > make -f "C...
2023 Aug 31
1
Problems with installing R packages from source and running C++ in R, even on fresh R installation
> This can be considered good news. You have just successfully performed > the job that is normally done by R CMD SHLIB when installing source > packages or running inline C++ code. The environment variables, at > least inside your running R session, are completely fine. > > Now we need to find out why R CMD SHLIB itself fails without producing > any output. Do you get any
2023 Aug 31
1
Problems with installing R packages from source and running C++ in R, even on fresh R installation
? 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 pr...
2023 Aug 31
1
Problems with installing R packages from source and running C++ in R, even on fresh R installation
> So starting a new Rcmd.exe process fails for some reason. > > If you take the same R session where the environment variables are > right and Sys.which() resolves Make and GCC and try to run > tools:::.shlib_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
2023 Aug 30
1
Problems with installing R packages from source and running C++ in R, even on fresh R installation
...re RStudio starts up _and_ that it isn't configured in your .Rprofile file. On August 30, 2023 12:10:28 PM PDT, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >On 30/08/2023 2:59 p.m., Ivan Krylov wrote: >> On Wed, 30 Aug 2023 16:31:20 +0000 >> Christophe Bousquet <chr_bousquet at protonmail.com> wrote: >> >>> So, yes, it seems possible for R to localize paths related to >>> Rtools... But then, I really do not get where things go wrong... >> >> When installing packages containing code to compile, R eventually calls >> R CMD...