similar to: HREFS for private packages - fixed? (PR#19)

For the (slightly) adventurous among you: We plan to roll out R 0.62.3 next Friday. In order to root out remaining bugs before the release, I'd like to encourage you to try it out on your system. Since there is a risk of destabilising things whenever you mess with the configure scripts, we won't attack installation problems on unusual platforms after this week. We also won't take

I put some documentation in a file dse/man/dse.Rd in and did R INSTALL -l rlibs dse This built the copies of dse.Rd in rlibs/dse/{help latex html}. It also wrote over R/doc/html/function.html and R/doc/html/packages.html, effectively clobbering all the R documentation. Also, the link that gets put in R/doc/html/packages.html points to R/library/dse/html/00Index.html rather than

The reason dse won't install is because of the new versioned install code. It assumes that it's dealing with a plain package, and doesn't handle bundles properly. Robert, could you look at that? A workaround is as follows. After the install.packages call fails with this message >Error in file(file, "r") : unable to open connection >In addition: Warning message:

I have my DSE library working fairly well now with 0.62.1. It required a few changes because of the changes to R INSTALL and "xxx<-" functions. I would like to tar up a new version soon but 1/ for testing I have been using a kludge in .First.lib to select the first element of section - since I happen to know that is the element I need given the way I have $RLIBS set. This argument

R-help -- I built R-2.2.1 in my own directory on a sun (solaris). Now I would like the sysadmin to move the contents to /usr/local/lib and place the binary in /usr/local/bin. No problem. However, the RHOME variable defaults to the directory from which R was built so it is not usable by anyone but me or ROOT. I would like to avoid building this again if possible. Any ideas? Thanks, Dan

As with 0.62.3, when I install my dse package with documentation in 0.62.4 the html help in R/doc/html/function.html gets clobbered so that the regular R function help is not available. I was postponing a revised version of my dse library install in the hope that this might be fixed. Does anyone know if this is a simple problem that I can hope will be fixed soon, or should I consider a

In Windows, I tried to build and check Paul Gilbert's dse bundle with the command rcmd check ../library/dse It ran for a while and built the packages, then failed at the end with this: ** checking Rd files ... OK ** checking for undocumented objects ... OK ** creating syskern-Ex.R ... ERROR I get similar errors checking packages, but there make pkgcheck-foo works. I don't

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

Since I have updated my Linux system, and consequently re-installed R, I am unable to see HTML documentation which I used to access via a web browser. To be more specific, my R installation is declared to be here: > R RHOME /usr/local/lib/R However, if I look at a location such as /usr/local/lib/R/library/base/html this contains only two entries File: 00Index.html File: R.css

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

On 17/11/2017 10:47 AM, Adelchi Azzalini wrote: > Since I have updated my Linux system, and consequently re-installed R, I > am unable to see HTML documentation which I used to access via a web > browser. To be more specific, my R installation is declared to be here: > > > R RHOME > /usr/local/lib/R > > However, if I look at a location such as >

Deepayan Sarkar <deepayan.sarkar at gmail.com> writes: > On Thu, Oct 29, 2015 at 2:09 PM, Rainer M Krug <Rainer at krugs.de> wrote: >> Dirk Eddelbuettel <edd at debian.org> writes: >> >>> On 28 October 2015 at 21:39, Marius Hofert wrote: >>> | Out of laziness I just used "R CMD batch" instead of "R CMD BATCH". I >>> |

I've put up R-0.62.0.tgz up for FTP from Auckland some minutes ago. As usual, don't get it from there unless you are desperate, but wait for it to be mirrored at a CRAN site near you within a day or two. Note that beginning with this version, you need Fortran in some form or other to compile R. (f2c is good enough) Here is the relevant part of the CHANGES file: CHANGES IN R VERSION

I've put up R-0.62.0.tgz up for FTP from Auckland some minutes ago. As usual, don't get it from there unless you are desperate, but wait for it to be mirrored at a CRAN site near you within a day or two. Note that beginning with this version, you need Fortran in some form or other to compile R. (f2c is good enough) Here is the relevant part of the CHANGES file: CHANGES IN R VERSION

I've put up R-0.62.0.tgz up for FTP from Auckland some minutes ago. As usual, don't get it from there unless you are desperate, but wait for it to be mirrored at a CRAN site near you within a day or two. Note that beginning with this version, you need Fortran in some form or other to compile R. (f2c is good enough) Here is the relevant part of the CHANGES file: CHANGES IN R VERSION

I've modified the "$RHOME/bin/R" and "$RHOME/cmd/filename" so that you can use the same directories for multiple machines. That is, machines running various flavors of UNIX can access the same directories. The modified structure adds the directories $RHOME/bin/$OSTYPE/ $RHOME/lib/$OSTYPE/ to hold the machine specific binaries. For instance, here the $RHOME directory

I've modified the "$RHOME/bin/R" and "$RHOME/cmd/filename" so that you can use the same directories for multiple machines. That is, machines running various flavors of UNIX can access the same directories. The modified structure adds the directories $RHOME/bin/$OSTYPE/ $RHOME/lib/$OSTYPE/ to hold the machine specific binaries. For instance, here the $RHOME directory

Dear all, I hope the following problem haven't been discussed here recently (I could not find anything about it the help archive files) : I tried to compile R-0.64.2 from the source files without much success... the last lines from the output of the ./configure command were : ---------------------------------------------------------- R is now configured for mips-sgi-irix6.4 Source

> On May 10, 2019, at 8:59 PM, Vitaly Buka via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Sorry for delay, I was busy with other stuff. > CTMark results. > > dse is the current DSE. > dsem is my experimental module level DSE. > dsem runs after dse, so it's additionally deleted stores. > > -O3 > dse - Number of stores deleted

Hi, Over the past six months, a MemorySSA-backed DSE implementation has been added to LLVM and it now covers almost all cases the existing DSE implementation does, plus adding a major new capability: eliminating stores across basic blocks. Thanks everyone involved with reviews, testing & patches! I think now would be a good time to start working towards switching to use MemorySSA-backed DSE