search for: rinstaller

As the build process, especially for Windows, is changing significantly for R 3.2.0, I am trying to build R-devel in preparation. When running `make rinstaller`, I get the following error: cp -p ../../../etc/x64/Makeconf R-devel/etc/x64 mkdir -p R-devel/doc cp -p ../../../doc/CRAN_mirrors.csv R-devel/doc mkdir -p R-devel/doc/manual/images cp -pR ../../../doc/html R-devel/doc cp -p ../../../doc/manual/*.html ../../../doc/manual/*.p...

On 26/01/2015 5:12 PM, Avraham Adler wrote: > As the build process, especially for Windows, is changing > significantly for R 3.2.0, I am trying to build R-devel in > preparation. When running `make rinstaller`, I get the following > error: > > cp -p ../../../etc/x64/Makeconf R-devel/etc/x64 > mkdir -p R-devel/doc > cp -p ../../../doc/CRAN_mirrors.csv R-devel/doc > mkdir -p R-devel/doc/manual/images > cp -pR ../../../doc/html R-devel/doc > cp -p ../../../d...

In R 0.63 RINSTALL of a package with documentation still appears to clobber R/doc/html/function.html and R/doc/html/packages.html so the main help is no longer available to a user once a package is installed. I know how to work around this for my own purposes, but I hesitate to release a package that would do this to some unsuspecting user. Paul Gilbert

After some investigation I find that "R INSTALL dse" seems to work well. Also, "R REMOVE dse" works but does not clean out ~/.R (which would be pretty difficult because all users may have this). The result is that a user will have the impression that the package is installed when it has be remove. (This is probably not too serious.) However, "R INSTALL -l rlibs

Hi, Having finally gotten around to installing R-2.9.0, I find that while the docs still say I can invoke the --no-latex option, R CMD INSTALL has decided that I can't. Nor is there any notice of this that I can find in the 2.9 series news. Is this just a trifling oversight that will be repaired? Jim

...eports the highest version in the range. If there are still non-digits in there it makes the version string "0" (not useful, but doesn't kill the build with a noninformative error message). I ran into another problem with the trailing 'M' from svnversion when doing 'make rinstaller' in R_HOME/src/gnuwin32: E:\R\R-svn\r-devel\src\gnuwin32\installer>type R-2.8.0dev.log Inno Setup 5 Command-Line Compiler ... Compiler engine version: Inno Setup 5.2.3 (ISPP 5.2.3.0) ... [ISPP] Preprocessing. ... [ISPP] Preprocessed. Parsing [Setup] section, line 1...

...ke distribution The last few lines from the make output is: Copying spatial find rw1070 -name CVS -prune -exec rm -rf \{\} \; FIND: formato de par?metros incorrecto make[2]: *** [imagedir] Error 2 make[2]: Leaving directory `/cygdrive/c/R/Rsource/R- 1.7.0/src/gnuwin32/installer' make[1]: *** [rinstaller] Error 2 make[1]: Leaving directory `/cygdrive/c/R/Rsource/R- 1.7.0/src/gnuwin32' make: *** [distribution] Error 2 So there seems to be a problem with find. I downloaded and innstalled the latest version of tools.zip today. Any idea of what is going wrong? Kjetil Halvorsen

...=$(CROSSDIR)/bin:$(CROSSDIR)/mingw32/bin:$(PATH); \ cd $(WINR)/$(R)/src/gnuwin32/; \ $(MAKE) recommended # dist-recommended: # mkdir -p $(WINRLIBS); \ # cd $(WINR)/$(R)/src/gnuwin32/; \ # $(MAKE) dist-recommended; \ # mv Recommended.zip $(WINRLIBS)/ clean: rm -rf $(WINR) #### not tested # rinstaller: # export PATH=$(CROSSDIR)/bin:$(CROSSDIR)/mingw32/bin:$(PATH); \ # cd $(WINR)/$(R)/src/gnuwin32/; \ # $(MAKE) rinstaller CrossCompileBuild : $(MAKE) down $(MAKE) xtools $(MAKE) prepsrc $(MAKE) mkrules $(MAKE) R

(I don't have time just now to diagnose & fix..) In R 0.63.3 [both on Solaris and Linux] > example(outer) Error: Couldn't find 'outer' example whereas this worked in 0.63.2. NON-exhaustive `research' [i.e. small sample out of about 1000]: o examples that stopped working (in 0.63.3 and did before) kronecker, outer, vector, Im o Examples working

On Sun, Mar 8, 2015 at 8:33 PM, Avraham Adler <avraham.adler at gmail.com> wrote: > > Thank you for the update, Hsiu-Khuern. Can you check how many digits > scientific notation shows? I was able to build a 64bit version of R > using the mingw64 4.8.4 distro, but ran into trouble with compat.c, > and the only work-around I found ended breaking R's defualt two digit >

I have built a version of the current 1.2.2 patched version of R using Inno Setup2 (http://www.jrsoftware.org/isinfo.htm). (That toolkit is open source (in Delphi) and was fairly easy to tame. Full details are in the R-patched sources.) This gives a single ~10Mb file, at http://www.stats.ox.ac.uk/pub/bdr/RWin/SetupR.exe The idea is that it should look very like a Windows 2000-style install, and

...the range. If there > are still non-digits in there it makes the version string "0" > (not useful, but doesn't kill the build with a noninformative > error message). > > I ran into another problem with the trailing 'M' from svnversion > when doing 'make rinstaller' in R_HOME/src/gnuwin32: > E:\R\R-svn\r-devel\src\gnuwin32\installer>type R-2.8.0dev.log > Inno Setup 5 Command-Line Compiler > ... > Compiler engine version: Inno Setup 5.2.3 (ISPP 5.2.3.0) > ... > [ISPP] Preprocessing. > ... > [ISPP] Preproce...

I tried for the first time to build R from source on Windows, where I got the source code via svn. Per the Installation and Administration manual, I altered src\gnuwin32\MkRules so it had the the locally correct paths to HTML Help Workshop and Inno Setup 5. I also set USE_SVNVERSION=yes, as suggested in MkRules itself. Then, while in the directory src/gnuwin32 I ran 'make all

Hi, I'm using plot.lda (R1.4.0 on linux) and, if dimen > 2, I get the error: Error in text.default(x, y, txt, cex = cex, font = font) : X11 font at size 16 could not be loaded The traceback indicates that the problem comes from pairs(). I've tried several cex and font values, always with the same error. The same command works fine with pdf() If I'm missing fonts, how

...; are still non-digits in there it makes the version string "0" > > (not useful, but doesn't kill the build with a noninformative > > error message). > > > > I ran into another problem with the trailing 'M' from svnversion > > when doing 'make rinstaller' in R_HOME/src/gnuwin32: > > E:\R\R-svn\r-devel\src\gnuwin32\installer>type R-2.8.0dev.log > > Inno Setup 5 Command-Line Compiler > > ... > > Compiler engine version: Inno Setup 5.2.3 (ISPP 5.2.3.0) > > ... > > [ISPP] Preprocessing. >...

...of that this would fail here is that GCC version 4.9 did make some changes to enhance link-time optimization [5], and probably something isn't compatible. I then downgraded to GCC 4.8.4 [6], and, with the deletion of those 10 or so lines from compat.c, I can complete the build straight through rinstaller. However, I get that failure issue due to the extra 0 in scientific notation [7]. It does not matter if I do the entire process in the MSYS2 environment, or if I do in in Windows with msys\usr\bin in my path. Na?vely, it seems that if there were some what for stdio to be included in compat.c, yet...

...rmail/r-devel/2014-December/070319.html > > >Many thanks to you and others for looking into this, >Henric > > > >> I then downgraded to GCC 4.8.4 [6], and, >> with the deletion of those 10 or so lines from compat.c, I can >> complete the build straight through rinstaller. However, I get that >> failure issue due to the extra 0 in scientific notation [7]. >> >> It does not matter if I do the entire process in the MSYS2 >> environment, or if I do in in Windows with msys\usr\bin in my path. >> >> Na?vely, it seems that if there were...

...>> >> >>Many thanks to you and others for looking into this, >>Henric >> >> >> >>> I then downgraded to GCC 4.8.4 [6], and, >>> with the deletion of those 10 or so lines from compat.c, I can >>> complete the build straight through rinstaller. However, I get that >>> failure issue due to the extra 0 in scientific notation [7]. >>> >>> It does not matter if I do the entire process in the MSYS2 >>> environment, or if I do in in Windows with msys\usr\bin in my path. >>> >>> Na?vely, it...

...>> >> >>Many thanks to you and others for looking into this, >>Henric >> >> >> >>> I then downgraded to GCC 4.8.4 [6], and, >>> with the deletion of those 10 or so lines from compat.c, I can >>> complete the build straight through rinstaller. However, I get that >>> failure issue due to the extra 0 in scientific notation [7]. >>> >>> It does not matter if I do the entire process in the MSYS2 >>> environment, or if I do in in Windows with msys\usr\bin in my path. >>> >>> Na?vely, it...

Hi Duncan, On Mon, Mar 9, 2015 at 10:40 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 09/03/2015 11:07 AM, Hsiu-Khuern Tang wrote: >> >> On Mon, Mar 9, 2015 at 3:50 AM, Duncan Murdoch <murdoch.duncan at gmail.com> >> wrote: >> > On 08/03/2015 10:02 PM, Hsiu-Khuern Tang wrote: >> >> Hi, >> >> >> >> [This