search for: makedl

...to build a package under windows (readme.packages is a great guide!), and it went all smoothly, except: option -free-form no longer was passed to g77 (from Rtools), which caused compilation to fail. Renaming Makevars to Makevars.win did not help. Investigating this in more detail, I found that MakeDLL contains the line <snip> FFLAGS=-O2 $(DEBUGFLAG) <snip> so PKG_FFLAGS weren't used at all. Changing this line to <snip> FFLAGS=$(PKG_FFLAGS) -O2 $(DEBUGFLAG) <snip> resolved the problem, however. I subsequently was again able to access the routines of the built librar...

...^^^^ > Notice the quotes! Same problem here (R-1.4.0, unstable, NT4). > > Not sure if it is a bug in R, in perl or in (what I presume) make. > To debug it, I took the relevant line from SHLIB (inserting the > variables): > > make -f d:/uwe-ns/R140-071201/src/gnuwin32/MakeDll > RHOME=d:/uwe-ns/R140-071201 DEBUG=T DLLNAME=pan CFSOURCES='pan.f' > CXXSOURCES='' RCOBJ= > make: *** No rule to make target `'pan.o', needed by `pan.a'. Stop. > > > Now leaving out quotes at some places: > > d:\uwe>make -f d:/uwe-ns/R140...

Dear R-help, I'm having problem creating a dll using Rcmd SHLIB with R-1.3.1 on WinNT4: C:\TEMP>Rcmd SHLIB tryf.o make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. C:\TEMP>Rcmd SHLIB tryf.f make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. I

Dear R-help, I'm having problem creating a dll using Rcmd SHLIB with R-1.3.1 on WinNT4: C:\TEMP>Rcmd SHLIB tryf.o make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. C:\TEMP>Rcmd SHLIB tryf.f make[1]: `libR.a' is up to date. make: *** No rule to make target `'tryf.o', needed by `tryf.a'. Stop. I

...s a pain. Then I worked that that copying just this list over from 2.8.1 is sufficient to restore R package cross-compiling ability: (half of these files are removed in 2.9.1, half are different) ------------------ share/perl/build-help-windows.pl share/perl/R/Rdlists.pm src/gnuwin32/ src/gnuwin32/makeDllRes.pl src/gnuwin32/Makefile src/gnuwin32/pwd.pl src/gnuwin32/MkRules src/gnuwin32/MakeDll src/gnuwin32/help/ src/gnuwin32/help/Makefile src/gnuwin32/MakePkg ------------------ Then I thought there must be a simplier way - most of R 2.9.1 isn't platform-sensitive any more (in fact that seems t...

Hi, all: I want to call a c program in the windows version R, so I installed ActivePerl and MinGw, wrote the code below in command prompt: Rcmd SHLIB filename.c and I got the error message as follows: Error: c:/R/rw1071/src/gnuwin32/MakeDLL 16: common syntax error. ..... There are errors on line 16 18 20 22 25 28 43 44 45 47 49 50 51 52 53 79 80 81 83. Has any one met the same problem before? Do I need other tools installed? Best Wishes, Guan Xing 9/20/03

Hello, I would like to build shared lib for R using cygwin environment. After installing needed tools (mainly perl, make and compilers), I ran R CMD SHLIB hw.c But I get the following error : $ R CMD SHLIB hw.c c:/PROGRA~1/R/R-26~1.2/src/gnuwin32/MakeDll:82: *** multiple target patterns. Stop. Google it didn't give me any hints. Thanks for your help. Sylvain Archenault. ************************************************************************* This message and any attachments (the "message") are con...{{dropped:13}}

...exe: 'a.out': No such file The reason is the empty list of dependencies in the pattern rule for DLLs contained in the file MkRules: %.dll: @$(ECHO) EXPORTS > $*.def @$(NM) $^ | $(SED) -n 's/^........ [BCDRT] _/ /p' >> $*.def The dependencies list is constructed in the MakeDll file that contains the following: CFSOURCES=$(wildcard -f *.c *.f *.f90 *.f95) CSOURCES=$(wildcard -f *.c) CXXSOURCES=$(wildcard -f *.cc *.cpp *.C) FSOURCES=$(wildcard -f *.f) FCSOURCES=$(wildcard -f *.f90 *.f95) OBJSA=$(foreach i,$(CSOURCES) $(FSOURCES) $(CXXSOURCES),$(basename $i).o) Observe t...

...and typing "make" I get: *** No rule to make target `../appl/ROUTINES', needed by `../include/FFDecl.h'. Stop. [exited with 2] (This was the same error I got under the origional b18 setup) Do these directories exist (and does FFDecl.h exist) ? The reason I ask is because in MakeDLL (for example) there are the lines include ../../../gnuwin32/MkRule and DLLLIBS=-L../../../gnuwin32 -l_iR -lf2c which seem to refer to directories on the wrong path (ie why ../../../) -- Douglas Steele -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mail...

Hi all, I am running R 2.6.2 in Windows XP with Rtools 2.7 and am trying to compile a shared library in Windows with customized level of optimization. Specifically, I would like to have "-O3 -funroll-loops" as flags when I run "R CMD SHLIB ***.cc" to speed the program for my simulations. I have read through the documentation and have tried adding the line PKG_CXXFLAGS =

Hi, I need to create a Makefile.win for a given package so as to fiddle slightly with the compilation process. My Makefile works fine in Linux but I am having trouble creating Makefile.win for MinGW. I first looked at the commands that Rcmd SHLIB appeared to be running and copied those onto the Makefile. But one step seems to be missing, the creation of the _res.rc file needed by windres

...ot * compile any .f file in acepack/src * (hence) try to create any dll file or libs (I'm working with Rw1000 under Win98, with the cygwin tools.) Looking into the MakePkg it looks like the following line LSOURCES=$(wildcard $(SSPKG)/*.c $(SSPKG)/*.f) produces a blank. Inside MakeDll there is another `wildcard' that also produces a blank: SOURCES=$(wildcard -f *.c *.f) Thanks for any hint, -Yudi- C:\R\rw1000\src\gnuwin32>make pkg-acepack /R/TOOLS/MAKE.EXE DLLNM= EXTRADOCS= \ -C /R/rw1000/src/library/acepack PKG=acepack RHOME=/R/rw1000 RLIB=/R/rw1000/li brary \...

...-cygwin was a my typos error > but I have to correct the readme.packages (--no-cygwin is a survival > from the about two year ago version of cygwin). The flag is set correctly in MkRules, though. > Anyway, note that in readme.packages we suggest to edit 'MkRules' > not MakeDll and to set at the beginning of that file 'BUILD=CYGWIN'. Of course! Apologies for my sloppy reading of MkRules. I tried to put in '-mno-cygwin' somewhere. > This then automagically sets the flags, and since it is the way > we build the binary distribution I hope we will...

Hi, All: I had some trouble debugging C source dynamically loaded into R , when I issued N in gdb(or insight) , the debugger, instead of moving downward step by step, jumped to strange positions (upward, downward, one step, a few steps away). To enter the debugger, I issued gdb(insight) Rgui.exe in Cygwin and add this line : asm("int $3"); to my C code. After entering R, I

...kg ---------- Making package acepack ------------ mkdir -p /R/rw1000/library/acepack cp -r ./DESCRIPTION ./INDEX ./TITLE ./ACE.DOC ./README ./README.ACE ./README .avas ./README~1.AVA ./WS_FTP.LOG /R/rw1000/library/acepack/ /R/TOOLS/MAKE.EXE -C ./src RHOME=/R/rw1000 \ -f /R/rw1000/src/gnuwin32/MakeDll DLLNAME=acepack g77 -O2 -Wall -c ace.f -o ace.o ace.f: In subroutine `mace': ace.f:89: warning: common /prams/ itape,maxit,nterm,span,alpha,big ^ Initial padding for common block `prams' is 4 bytes at (^) -- consider reorderin g members, largest-type-size first a...

...-c directory but not a src one. The option DLLNAME=yyy must be used if the package requires a dll with a name different from xxx.dll. For example, the dll of integrate is adapt.dll. If you don't need the two flags, you can use the short command > make pkg-xxx Compiler flags must be setted in MakeDll. Look to this file for some example. Help files There are no support for generating the help files. You have to download the pre-formatted one by any CRAN site or to build them yourself on a Unix machine. Tools To rebuild the system and to install other packages, you need not only a compiler bu...

...-c directory but not a src one. The option DLLNAME=yyy must be used if the package requires a dll with a name different from xxx.dll. For example, the dll of integrate is adapt.dll. If you don't need the two flags, you can use the short command > make pkg-xxx Compiler flags must be setted in MakeDll. Look to this file for some example. Help files There are no support for generating the help files. You have to download the pre-formatted one by any CRAN site or to build them yourself on a Unix machine. Tools To rebuild the system and to install other packages, you need not only a compiler bu...

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

Dear R-people: I tried to create a shared library in Windows XP. However I got error messages which attached below: C:\lasso>Rcmd SHLIB all.f cox.f gcc all.o libR makeMakedeps all.dll -o all gcc.exe: libR: No such file or directory gcc.exe: makeMakedeps: No such file or directory make: *** [all] Error 1 I have created shard libraries successfully before. Also for the same fortran files:

...001). There is also a shell script Rd2dvi.sh which you can use if you have sh.exe (as used to compile packages) and latex etc. The environment variable XDVI sets the previewer, defaulting to xdvi.bat. A file `Makevars' in the `src' directory of a package can be used to add to/override the MakeDll makefile used to make foo.dll, as on Unix. (See `Creating shared libraries', section 3.4 of `Writing R Extensions'.) Under rare conditions (lots of very short input lines) the history buffer could overrun and so cause crashes. This has been possible since rw0623, but first caused reported...