similar to: Makefiles and other customization

I've made a package for which R CMD build isn't producing very satisfactory results. I'll get to the details in a moment. I wonder if it would make sense to have my own makefiles (which already exist and are doing quite a lot) produce the .tar.gz file ordinarily produced by R CMD build. As far as I can tell, R CMD build basically tars up of the project directory after running some

I am building from source on RHEL 4 and have run into a problem while running "make check": running code in 'lapack.R' ...make[3]: *** [lapack.Rout] Error 1 make[3]: Leaving directory `/opt/R/R-2.9.1/tests' make[2]: *** [test-Specific] Error 2 make[2]: Leaving directory `/opt/R/R-2.9.1/tests' make[1]: *** [test-all-basics] Error 1 make[1]: Leaving

The contents of .Rbuildignore seems to affect R CMD build but not R CMD check. I'm using R 2.4.0 on Debian. Is my understanding correct? And is there anything I can do about it? In my case, some of the excluded files contain references to other libraries, so linking fails under R CMD check. I realize I could add the library to the build (with Makevars, I guess), but I do not want to

Dear list, When compiling the R-2.3.0 on FC4 x86_64, I got the following errors: make[3]: Entering directory `/project/scratch3/ligroup/wuming/src/R-2.3.0/src/main' gcc -Wl,--export-dynamic -L/usr/local/lib64 -o R.bin Rmain.o CConverters.o CommandLineArgs.o Rdynload.o Renviron.o RNG.o apply.o arithmetic.o apse.o array.o attrib.o base.o bind.o builtin.o character.o coerce.o colors.o complex.o

When a generic (S4) has an argument with a default followed by ..., missing() doesn't seem to work if the method omits the ... --------------------Sample------------------------------- foo <- function(x, y=0, ...){ "you are very generic" } # no ... in function arguments setMethod("foo", signature="character", function(x, y=0){ if (missing(y))

I have some questions about building packages in Windows when using .Rbuildignore . The part of the process that is of interest here is the part that creates the source tree from the tree that contains the .Rbuildignore file. That is, the part of the process that does a build of the original tree creating a .tar.gz and then extracts this file into a source directory that can be used by check,

I am trying to get R-2.2.1 to pass make check on an AIX 5.2 at work (I know R-2.2.1 is not the latest release, but I encountered make errors in my attempts to install either R-2.3.0 or the R-patched_2006-05-10 on the version of AIX I am on. I will post those errors in a separate posting from this.) So far, configure and make finish without error for R-2.2.1 using gnu make, gcc-4.1.0, and

Fascinating. Or, well, not. Failing to use a method signature that is compatible with the generic is a no-no. So your bug seems to me to be outside the bounds of how R is supposed to be used. So don't do that. On April 17, 2024 4:25:38 PM PDT, "Boylan, Ross via R-help" <r-help at r-project.org> wrote: >When a generic (S4) has an argument with a default followed by ...,

On Thu, 18 Nov 2004 00:38:47 +0000 (UTC), Gabor Grothendieck <ggrothendieck@myway.com> wrote : >DIFFERENCE BETWEEN USING .RBUILDIGNORE AND NOT > >The reason that the processing is different according to whether one >uses .Rbuildignore or not is that > R CMD build >takes the .Rbuildignore file into account but > R CMD install > R CMD check > R CMD build

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 -

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

Example input and output to reproduce this can be found at https://gist.github.com/jimhester/b7f05f50794c88e44b17. I tested this attempting to compile the [digest]( http://cran.r-project.org/web/packages/digest/index.html) package, `run.sh` and `run.bat` were both run in the package source directory on Ubuntu 14.01 and Windows 7 respectively. In particular while the `CFLAGS` values were properly

Hi all, I have Win XP and R 2.3.1 on my notebook. I would like to write a package which includes some Fortran 95 code. Interestingly, if I compile and link the simple file test90.f90 directly with g95 -c test90.f90 g95 -shared -o test90.dll test90.o then PE Viewer ( a dll viewer) shows me the right functions in the export table, hence I can use the dll in R. But as it should become part of a

I was trying, on a Linux system, to get a .Rbuildignore file to work. After far too long, I found the problem was the <CR><NL> line endings in the .Rbuildignore file -- I had originally created it on a Windows system, and emacs in Ubuntu was politely hiding that fact from me. The patterns didn't work to exclude files because it was trying to match filenames to patterns like

To get RSPython installed on my debian test box, I had to make a couple of changes not listed in ftp://www.omegahat.org/pub/Omega/RSPython/FAQ.html 1) I had to change $R_HOME/src/modules/X11 : $(R_X11_la): $(R_X11_la_OBJECTS) $(R_X11_la_DEPENDENCIES) $(SHLIB_LINK) -o $@ $(R_X11_la_LDFLAGS) $(R_X11_la_OBJECTS) $(R_X11_la_LIBADD) $(LIBS) to $(R_X11_la): $(R_X11_la_OBJECTS)

On Mar 19, 2008, at 2:55 PM, Bill Wendling wrote: > Thanks, Mike! I applied this to the tree. No, you applied something else to the tree! :-) I had a space before the \ and after the ". The below should fix it. Doing diffs in .: --- ./Makefile.in.~1~ 2008-03-19 15:45:54.000000000 -0700 +++ ./Makefile.in 2008-03-19 16:30:07.000000000 -0700 @@ -1689,7 +1689,7 @@ libgcc.mk:

I've changed to Mercurial for my working copies of survival for a number or resons not relevant to this post. When I do R CMD check, I get some warnings about certain files in the .hg directory with odd names. I've added the following 2 lines to my .Rbuildignore file without effect ^\.hg$ ^\.hg.* I'm not a Perl user so perhaps I'm reading the help page wrong. Any pointers? This

Hello, I tried to compile v2.3.1 on Solaris x86 with SUN Pro compilers. I had an error while stats libarary was being compiled and I notice that "-xtarget=generic64" was not passed to f95 while cc used it. Could you tell me how to fix this problem? f95 -PIC -O -I/mounts/devel/SUNWspro/prod/include -c sgram.f -o sgram.o f95 -PIC -O -I/mounts/devel/SUNWspro/prod/include -c

To all. I need your help. The big question is: How do I make an R library with Fortran 95 files? You may assume that I am a pretty decent programmer in both R and Fortran. I lay out a scenario and need your help! I know how to make an ordinary R package and have dabbled with R + Fortran 95 *.dll linking. I do not have a great handle on the whole Makevars file and whatever else I might need

I've installed hdf5 [library & includes] here locally, last week. [see ?hdf5save in R] There is a remaining compilation / linking problem for me: The hdf5 library uses "compress2" a routine defined in Gnu's zlib, but not available in the zlib that comes with X11R6.3 (which we have installed). Now unfortunately, the final link statement for R (0.65) [for me, with hdf5