similar to: R-beta: makefile command line for recreating dynload demo dll

recently I used gcc 4.9.1 (http://sourceforge.net/projects/mingw-w64/files/Toolchains targetting Win64/Personal Builds/mingw-builds/)on windows to build R,but failed when link R.dll ,it report linker status 5.  after some digging, I found when use gcc 4.9.1 64 bit on windows there are lots of .refptr.*(* is r function name) in R.def, which lead build fail.so I add a simple path to

>This mean that the specs file of Cygnus gcc is different from the >mingw32 one. OK thanks (I added main() {} as per FAQ and I got the dynload to build a dll ok) I am also interested in building the R sources as per your descriptions. To simplify things, I have removed b18 cygwin and have now installed egcs-mingw32 with your djtools as recommended. Everything seems to work OK; tools that

Hello Dear R Developers and Users: I'm trying to compile R with all the tools of the CRAN page. I compile the R-1.2.2 version without problem. But when I try to compile the development version 1.3.0 it doesn't work when I write the command: make BUILD=MINGW32 First it shows me something like this (I think without problems): As I make when I compile succesfuly the R-1.2.2 version:

Hello Dear R Developers and Users: I'm trying to compile R with all the tools of the CRAN page. I compile the R-1.2.2 version without problem. But when I try to compile the development version 1.3.0 it doesn't work when I write the command: make BUILD=MINGW32 First it shows me something like this (I think without problems): As I make when I compile succesfuly the R-1.2.2 version:

Hi all, (Originally posted to r-help) I'm porting a package that I've worked on for OS X to Windows. The package is written in F95 so I need to compile it with gfortran and link it with gcc4. I've been trying to build an R with gcc4 without luck so far. If there is a binary of such a thing info would be appreciated. This package requires a Makefile. My question is, how can I find

Hi, I've been trying to get the python bridge (rpy2) to build for 64-bit R and python. The current stumbling block is that mingw can't use the python27.lib file that comes with CPython and so I need to generate libpython27.a. When I use dlltool from rtools to do that however, I end up with a 32-bit file: >"G:\Rtools\gcc-4.6.3\i686-w64-mingw32\bin\dlltool" -e libpython27.a

Ok, one last try. R1.2.0, WinNT 4.0: [R is installed in: R_HOME=D:\Programme\R\rw1020] Can anyone give a hint what the following error message (when running Rcmd INSTALL) means and what to do about it? cd D:\Programme\R\rw1020\src\library D:\Programme\R\rw1020\bin\rcmd install testfunctions make: Entering directory `/cygdrive/d/Programme/R/rw1020/src/gnuwin32' dlltool -k --as as --dllname

Full_Name: Heinz Grimm Version: R1.5.1 OS: Windows NT Submission from: (NULL) (195.65.178.178) Line 11 is: "DLLLIBS=-L'c:/jdk1.3/lib' -L$(JAVA_HOME)/jre/bin/hotspot...." should be: "DLLLIBS=-L$(JAVA_HOME)/lib -L$(JAVA_HOME)/jre/bin/hotspot...." Line 59 is: " (cd .. ; ./configure.win $(RHOME))" should be: " (cd .. ; sh ./configure.win $(RHOME))"

When I use the -v I can modify the size of the heap, as assessed by gc(), but the -n key seems to be without effect ? On a machine with 48 mB ram I can load the libraries without problem, but on my own 36 mB ram machine, I get dynload problems with the larger, eg survival4. Any suggestions ? Troels -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list

When I use the -v I can modify the size of the heap, as assessed by gc(), but the -n key seems to be without effect ? On a machine with 48 mB ram I can load the libraries without problem, but on my own 36 mB ram machine, I get dynload problems with the larger, eg survival4. Any suggestions ? Troels -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list

Hello R Developers, This is my first foray into using c-code with R, so please forgive my foolishness. I had a look at the archives and did not find anything on this, so hopefully I am not doubling up. I have tried to use R cmd to create an object file from the odesolve dynload example. I am using windows and have just installed rtools, and have the latest version of stable R (2..7.2). This is

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 R Gurus, > This is my first foray into using c-code with R, so ... > I had a look at the archives and did not find anything on this, so > hopefully I am not doubling up. > I have previously used the following approach where I needed some very small numbers/large (using Brobdingnag): surfacewithdiff <- function(t, y, p) { const=p["const"] kay

On Thu, 10 Jun 1999, Friedrich Leisch wrote: > Yes, if I understood AIX workings correct you have to have a text file > of to-be-exported symbols at the time of linking a shared library, > i.e. the linker is called like (this is pasted from a mail by Arne) > > $(F77) -o module.so -bM:SRE -bE:module.exp -bnoentry $(OBJECTS) $(LIBDIR) $(LIBS) > > where module.exp is a text

-- 此致 礼 罗勇刚 Yours sincerely, Yonggang Luo -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161115/80fd3c17/attachment.html>

I get an error: Error in dyn.load(file) : unable to load shared library "D:\R_CODA\RW0613\library\eda\libs\eda.dll" with almost all the packages. I tried to use "require" and tried also to copy the dll's to the bin directory and nothing helped. Any ideas ? Thanks for your efforts Troels -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help

I originally posted on this topic on a different thread: https://stat.ethz.ch/pipermail/r-devel/2016-August/072938.html These sources suggested that a safe practice might be to put double quotes around symbol names in EXPORTS in case the symbol name is the same as a linker keyword: - https://sourceware.org/binutils/docs/ld/Symbols.html#Symbols -

I am using rw0613b with djtools on Win95. No problem with makefiles building fortran and C dll's, plus can build R.exe with the supplied libraries (including mva). Why then do I get the following error when I try to building an existing library separately, eg... (/R-0.61.3/src/gnuwin32)$ make -f MakePkg -C ../library/mva PKG=mva make.exe: Entering directory `c:/R-0.61.3/src/library/mva'

Ok, I think I may have a path or permissions problem (below). Anyone know which settings I should check? When I use "Rcmd SHLIB <filename>" I get: C:\Program Files\R\rw1081\bin>Rcmd SHLIB info.diffusion.c process_begin: CreateProcess((null), dlltool -k --as as --dllname R.dll --def R. exp --output-lib libR.a, ...) failed. make (e=2): The system cannot find the file

Hello, I wanted to test the odesolve package and tried to use compiled C-code. But when I do: erg <- lsoda(y, times, "mond", parms, rtol, atol, tcrit=NULL, jacfunc=NULL, verbose=FALSE, dllname="mond", hmin=0, hmax=Inf) I get the error message: Error in lsoda(y, times, "mond", parms, rtol, atol, tcrit = NULL, jacfunc =