similar to: R-beta: info on dyn.load

It does, at least for a while. But when various more or less well behaved programs enter the scene (harddisk) things changed, at least for me. Reinstallation of R or windows didn't help, and I did not want to start again from scratch with a reformat. I used rw0613. -----Oprindelig meddelelse----- Fra: Douglas Steele <Douglas at dsteele.demon.co.uk> Til: r-help at stat.math.ethz.ch

Hi Guido, As you may have seen from my other message, I am now running Win95 B but am still getting the dyn.load failure already reported. So far as I can see, the problem is in the DLL files, not the R.exe. I have two versions, your version built with the cross-compiler, and one built with Mingw32 version 1.02 (1.1 has an additional problem). Your cross build version works fine. My locally

Hi, Win95 version, trying to build multiv. Following error (no mention in faq etc, but someone may have mentioned it recently). Appreciate any help. ------- Building multiv.dll from multiv.a -------- echo LIBRARY multiv > multiv.def echo EXPORTS >> multiv.def nm multiv.a | sed -n "/^........ [DT] _/s/^........ [BCDRT] _/ /p" >> multiv.def gcc -mdll

I have C routines in a collection of files "/homef/jonm/postdocs/GLMM_project/Cprogs/nn/misc.o" "/homef/jonm/postdocs/GLMM_project/Cprogs/nn/random.o" "/homef/jonm/postdocs/GLMM_project/Cprogs/nn/ars.o" ... etc , where the third file includes functions which call functions in the second. In S, the function > gload function() {

(Win95, v62.3, Guido's port.) The graphapp based console seems a definite improvement. Screen output is much faster. History mechanism present. Can now build whole system because windres not required. Spin-off is that graphapp can be used for completely different applications. A couple of problems. When R started and then library(pkg), get message (not every time though) that pkg unable

I am currently running R under Windows95. I am entirely new to R in any environment, with no prior experience of S or S-Plus either. I want to run some functions written for S-plus and residing in a file "cat.s". The fuctions also call some Fortran routines residing in a compiled fortran file "cat.obj" In S-Plus as I understand it I am supposed to first

In S(plus), I can write functions using code fragments like if(!is.loaded(symbol.C("my_C_fun"))) dyn.load("......../my_C_fun.o") r <- .C("my_C_fun", x = x, n = n, ... ) which I would like to have in R, too. The S-plus help page on this subject says : S+>> Code Availability S+>> S+>> DESCRIPTION: S+>> is.loaded

I'm trying to install R on a Red Hat 3.0.3 system, but cannot seem to get dyn.load() to fuction. The configure script says: checking for dlopen in -ldl... no And compiling fails at ../lib/libunix.a Any suggestions? What should I do to be able to use dyn.load()? I cannot upgrade the system to a higher version of Red Hat, but I will probably get away with installing some new

Hi, I have been trying to dyn.load a library (rq.obj), which will allow me to run a quantile regression function, but so far unsuccessfully. I have tried under windows 98 and R 6.24: 1) dyn.load("d:\\...\\rq.obj") 2) dyn.load("d:\...\rq.obj") 3) 1 and 2 accounting for case sensitivity. 4) dyn.load("d:/.../rq.obj") 5) Place the files in the directory where from I

Hi, when designing libraries for R, is it possible to call C/Fortran subroutines from other dynamically loaded code? The following example crashes R: ********* fn1.c ***************** void twice(int *i) { *i = 2 * *i; } ********************************* ********* fn2.c ***************** extern int twice(int *i); void negtwice(int *i) { *i = -1 * twice(i); }

Hi, when designing libraries for R, is it possible to call C/Fortran subroutines from other dynamically loaded code? The following example crashes R: ********* fn1.c ***************** void twice(int *i) { *i = 2 * *i; } ********************************* ********* fn2.c ***************** extern int twice(int *i); void negtwice(int *i) { *i = -1 * twice(i); }

After having browsed the documentation for a while without discovering what I am looking for, maybe one of you would know ... What I want to do: I have two fortran files MC.f and ESCA.f. In MC.f there is a call to a routine called lpost. This routine (lpost) is defined (among other things) in ESCA.f. Under linux, I can do the following: R CMD SHLIB MC.f and R CMD SHLIB ESCA.f followed by

Hello: I am having some difficulty with a DLL, using > version _ platform i386-pc-mingw32 arch x86 os Win32 system x86, Win32 status major 1 minor 2.1 year 2001 month 01 day 15 language R I have a library called

Hello, I am observing the following strange behavior when I try to load a shared library using dyn.load() under Linux... The library foo.so refers to a symbol in another package bar (with shared library bar.so), I get: dyn.load('foo.so') # error message because I forgot to load bar library(bar) # so I fix it dyn.load('foo.so') # works this time and everything is fine But, if

Hi, here are a couple of strange things happening with R.2.2.0 compiled under Mandrake-10.1 At the begining of the story I have segmentation fault using package RandomFields in conjuction with some Fortran code of mine loaded with dyn.load. One of my fortran programs contains a subroutine named fstat Trying to trace , I simplified the sequence as much as possible and I end up with the the

Hi, I'm using dyn.load to load a shared library (compiled from C code) into R. If I dyn.unload it and then dyn.load it again, I get an hourglass icon in Rgui (R 1.7.0, Win 2000), and it just sits there forever. I can't press Escape to stop the current computation, but I can close Rgui without resorting to using the Task Manager. Is it a problem with my use of R_alloc? Do I need

Hello, In such cases, with C code, I call dyn.unload before loading the modified shared lib again. I don't know if this changed recently, but it used to be needed or else R wouldn't load the new lib. When I call dyn.unload followed by dyn.load I never had problems. (Or the other way around, call dyn.unload before modifying the C code.) Hope this helps, Rui Barradas On 3/1/2018 8:52

Good question Rolf. Rui, thanks for pointing out dyn.unload. When I started using Rcpp a couple of years ago I got burned by stale .so enough times that I adopted a policy of recompile-then-start new R session. My workflow does not include Rolf's "brazillion" repeats, so the overhead of this approach has not been too painful. The documentation for dyn.unload (via ?dyn.unload)

I sent this enquiry to r-help and received several sympathetic replies, none of which were definitive. It was kindly suggested to me that I might get better mileage out of r-devel, so I'm trying here. I hope that this is not inappropriate. My original enquiry to r-help: ========================================================================== I am working with a function "foo"

Hi, here are a couple of strange things happening with R.2.2.0 compiled under Mandrake-10.1 At the begining of the story I have segmentation fault using package RandomFields in conjuction with some Fortran code of mine loaded with dyn.load. One of my fortran programs contains a subroutine named fstat Trying to trace , I simplified the sequence as much as possible and I end up with the the