For completeness, I also just tried the R 2.1.1 snapshot from yesterday with
gcc-4.0, g++-4.0 and gfortran-4.0 in an up-to-date Debian unstable chroot --
no issues to report from the build and regression test.
Haven't run that version as I currently do not have a system running
unstable, though.
On 27 June 2005 at 17:33, Earl F. Glynn wrote:
| "Seth Falcon" <[EMAIL PROTECTED]> wrote in message
| news:[EMAIL PROTECTED]
| > On 27 Jun 2005, [EMAIL PROTECTED] wrote:
| > > I only wish the Bioconductor E-mail somehow got on the gmane
| > > "newgroups" too.
|
| After my post I discovered the Bi
Duncan Murdoch stats.uwo.ca> writes:
> On 6/30/2005 8:10 AM, Gabor Grothendieck wrote:
> > When I install a new version of R (Windows XP) I have to:
> >
> > 1. copy my rw\etc\Rprofile.site file to the new installation
Same here, and I also change one or two things in etc/Rconsole. It would
On 17 July 2005 at 17:29, Ayal Pinkus wrote:
| Do you have cvs, and the possibility to compile under Windows?
Yes on both counts, though CVS got replaced by SVN.
R builds fine under Windows (though you need to pay attention to the details
which are in the (binary) distribution in the pdf files,
On 17 July 2005 at 20:55, Ayal Pinkus wrote:
| > R builds fine under Windows (though you need to pay attention to
[...]
| Ok. Unfortunately I work on a Mac OS X at home (I have access to
| Windows, MS DevStudio
Why didn't you say so earlier? :)
I don't do Mac OS X, so can't help. There is a
On 31 July 2005 at 03:53, [EMAIL PROTECTED] wrote:
| Full_Name: P Kapat
| Version: 2.1.1 (2005-06-20)
| OS: GNU/Linux 2.6.8-2-386, Debian testing
| Submission from: (NULL) (65.24.56.41)
|
|
| Relevant Bugs Ids : 7987, 7989
|
| H is a 100x100 singular but symmetric matrix (a matrix defining the
Göran,
On 20 August 2005 at 13:54, Göran Broström wrote:
| I have both gcc-3.4 and gcc-4.0(.1) installed on my system
| (debian-amd64 unstable), with links /usr/bin/gcc, g77, etc. to
| the 3.4 versions. When I build R, the 3.4 version is picked up,
| which is fine.
|
| However, when I 'install
On 16 October 2005 at 14:04, Prof Brian Ripley wrote:
| whereas I have seen some Qt-based ones I really liked.
Qt is C++, cross-platform using native widgets on OS X and Win and (since
more recently) available without fee or license woes provided it is used for
GPL'ed code.
So it satisfies b
On 5 November 2005 at 22:52, R S Ananda Murthy wrote:
| I tried to do make install DESTDIR=$PKGDIR. But this does not work. What
| is the alternative? I need to do this to create Slackware package.
I think you want
make prefix=$PKGDIR install
as the documentation in R-admin states rath
On Tue, Dec 13, 2005 at 09:48:56PM +, Prof Brian Ripley wrote:
> Does anyone have a need to use f2c rather than a Fortran compiler to build
> R?
We used f2c up until a few months ago as a last line of defence against
crappy Fg77 code on m68k/arm (one or both, it changed at times).
I'd be hes
stats.ox.ac.uk> writes:
> Can you confirm you are running rl5.1? Given the segfault is readline not
Yes: readline 5.1, just like the bug submitter (see at the very bottom).
> compatible version of a dynamic library so it seems to me the bug should
> be assigned to readline not R.
Looks like
On 22 December 2005 at 17:19, Duncan Temple Lang wrote:
| Michael Lawrence has as part of RGtk2.
Speaking of which -- I tried to find his code anywhere on the "Internets"
following his very nice DSC presentation, but no beans. Why is this in
hiding? Is it expected to surface at some point? Any
On Wed, Dec 21, 2005 at 02:48:25PM +, Dirk Eddelbuettel wrote:
> stats.ox.ac.uk> writes:
> > Can you confirm you are running rl5.1? Given the segfault is readline not
>
> Yes: readline 5.1, just like the bug submitter (see at the very bottom).
And a new Debian versio
Andrew Finley umn.edu> writes:
> I am in the process of writing an R extension in c++ and am using several
> STL containers (e.g., vector, map, multimap double>). I make sure to clear all these containers at the end of the
> .Call. Everything compiles and runs just fine, but I'm a bit worried
On 13 January 2006 at 11:02, [EMAIL PROTECTED] wrote:
| Is there any way to save a plot produced by
| R in a LINUX (Debian) machine?
It is the same on every platform and ...
| The window opened by R to put the plot in,
| does not give any option to save it (there
| are options to move, close, mi
On 22 January 2006 at 18:26, Marjo en Edwin wrote:
| I am wondering if there are any plans for incorporating the option to save
| graphs as ".svg" files. This would make it easy to postprocess figures in R
| with Inkscape, the open source vector graphics editor.
Had you run this search from withi
On 26 December 2017 at 15:24, Sun Yijiang wrote:
| After looking into C source code, I found that Rscript by default fills
| environment variable R_DEFAULT_PACKAGES with
| "datasets,utils,grDevices,graphics,stats", and it somehow fails some
| package like h5.
|
| The problem here is, not setting
On 26 December 2017 at 22:14, Sun Yijiang wrote:
| Thanks for the solution. Now I know the work-arounds, but still don't
| quite get it. Why does R_DEFAULT_PACKAGES has anything to do with
| library(methods)?
Because it governs which packages are loaded by default. And while R also
loads 'metho
Duncan,
Very nice tutorial. However it does NOT take away from the fact that _very_
simple_ scripts (like the one posted by Sun at the beginning of this thread)
simply _fail_ in error under Rscript.
Whereas they don't under R or r.
The R environment ships an interpreter meant for command-line a
On 29 December 2017 at 07:23, Therneau, Terry M., Ph.D. wrote:
| The submission guide has the following cryptic (to me) sentence:
| "Reasonable compression should be used for data (not just .rda files) "
|
| The survival pacakge has a fairly large number of data files --- exactly what
should
On 29 December 2017 at 07:59, Therneau, Terry M., Ph.D. wrote:
| which is already taken care of)." The survival package has about 2M of .rda
files and
| 2.2M of vignettes so I'm still under the 5M boundary, but R CMD check nags
about it.
The nags are genuinely irritating, especially as they a
On 20 January 2018 at 10:43, Patrick Perry wrote:
| As of R Under development (unstable) (2018-01-19 r74138):
|
| > as.character(list(NA))
| [1] "NA"
|
| > is.na(as.character(list(NA)))
| [1] FALSE
Are you aware that this is the same in R-release, and might be "on purpose" ?
R> R.Version()$v
On 25 January 2018 at 06:20, Duncan Murdoch wrote:
| On 25/01/2018 2:57 AM, Iñaki Úcar wrote:
| > For what it's worth, this is my workflow:
| >
| > 1. Get a fork.
| > 2. From the master branch, create a new branch called fix-[something].
| > 3. Put together the stuff there, commit, push and open
On 29 January 2018 at 11:02, Mark van der Loo wrote:
| I discover a lot of packages not by explicit search, but by running into
| them. I find cranberries really helpful there, especially the twitter feed
| (@CRANberries) and also r-bloggers, especially through Joseph Rickert's
| monthly roundup o
Mehmet,
That is a loaded topic, not unlikely other topics preoccupying us these days.
There is package.skeleton() in base R as you already mentioned. It drove me
bonkers that it creates packages which then fail R CMD check, so I wrote a
wrapper package (pkgKitten) with another helper function (k
I have received three distinct (non-)bug reports where someone claimed a
recent package of mine was broken ... simply because the macOS binary was not
there.
Is there something wrong with the cronjob providing the indices? Why is it
pointing people to binaries that do not exist?
Concretely, file
(Please do not quote without attribution)
On 30 January 2018 at 20:44, Hadley Wickham wrote:
| Personally, I think the biggest problem with package.skeleton() is
| that it assumes that the source of truth is objects in an environment.
| This seems the wrong way around to me.
Basically irrelevant
Bumping this as we now have two more issue tickets filed and a fresh SO
question.
Is anybody looking at this? Simon?
Dirk
On 30 January 2018 at 15:19, Dirk Eddelbuettel wrote:
|
| I have received three distinct (non-)bug reports where someone claimed a
| recent package of mine was broken
On 17 February 2018 at 21:10, Hugh Parsonage wrote:
| I was told to re-raise this issue with R-dev:
|
| In the documentation of R-dev and R-3.4.3, under ?gsub
|
| > replacement
| >... For perl = TRUE only, it can also contain "\U" or "\L" to convert
the rest of the replacement to upper or l
On 13 March 2018 at 17:29, Christophe DUTANG wrote:
| So, I was wondering if this warning was removable at all? Does anyone
encounter this issue?
That is a pretty old topic.
Did you look into Writing R Extensions? The first mention is
* Do be very careful with passing arguments between R,
What OS are you on? On Ubuntu 17.10 with R 3.4.3 all seems well (see
below for your example, I just added a setwd()).
[ That said, I long held a (apparently minority) view that csv is for all
intends and purposes a less-than-ideal format. If you have that much data,
you do generally not want to
On 23 April 2018 at 12:33, Peter Simons wrote:
| Hi,
|
| I just tried to upgrade Nixpkgs to R 3.5.0, but unfortunately the new
| version fails its regression test suite. We configure the build using
| the flags "--without-recommended-packages", in case that's relevant. You
| can see a complete bu
On 23 April 2018 at 15:14, Peter Simons wrote:
| Duncan Murdoch writes:
|
| > You can likely get rid of most of them by building with the recommended
| > packages.
|
| unfortunately, this is not an option for us. For various reasons, our
| build process requires that we build those packages s
Peter,
I think we are on the same page, but there is little I can do for you here.
Ultimately you are asking R Core to do you a favor. More below.
On 23 April 2018 at 18:28, Peter Simons wrote:
| Hi Dirk,
|
| > I have been doing for R for about 20 years (if you count the time I
| > assisted D
On 9 May 2018 at 10:37, Tomas Kalibera wrote:
| And for that reason the behavior should be as intuitive as possible when
| designed. What was intuitive 15-20 years ago may not be intuitive now,
| but that should probably not be a justification for a change in
| documented behavior.
Time for do
As you may know, I look after the R package for Debian. My fellow Debianers
make me follow a specific protocol -- a so-called "transition" in which all
dependent packages on an identified potential breakge are rebuilt under the
new (potentially breaking) change. We started adding an r-api-3.4 tag
On 4 June 2018 at 20:06, Tomas Kalibera wrote:
| thanks for the report. Access to the test system is not necessary, the
| memory requirements of the byte-code compiler are usually
| platform-independent and specifically with this package I can reproduce
| they are very high. We'll have a look
On 25 July 2018 at 21:04, Stephen Marsh wrote:
| So the Homebrew community dropped support for --with-cairo which is a shame
| because --without-x --with-cairo is an important combination for any
| environment that might need to generate graphics without X11 (or related)
| dependencies (macOS, he
On 30 July 2018 at 05:35, David Hugh-Jones wrote:
| Hi guys,
|
| Perhaps someone here can help.
|
| I am trying to build versions of R 1 for the rcheology package (just
| arrived on CRAN).
|
| For R prior to 1.5.0, I cannot configure support for tcl-tk.
|
| I am building on Debian Woody (prov
On 30 July 2018 at 16:26, David Hugh-Jones wrote:
| Thanks for the tip. That could be a huge timesaver. But it lists only a
| single package for versions 0.90.1-2 ... how does that work?
The lookip is source or binary-package based. Eg here are three binaries
built from source 'r-base':
http:
On 8 August 2018 at 12:40, Hadley Wickham wrote:
| I think this is true in the tidyverse, which will never give you a
| factor unless you explicitly ask for one, but the default in base R
| (at least as soon as a data frame is involved) is to turn character
| vectors into factors.
False. Base R
On 9 August 2018 at 20:37, Tomas Kalibera wrote:
| So to answer your original question, this could probably be handled in
| Rcpp,
Hm. Why do you say that / what did you have in mind?
Recall that we do not alter SEXPs or introduce additional additional
reference counters -- because we do not th
On 9 August 2018 at 14:13, luke-tier...@uiowa.edu wrote:
| On Thu, 9 Aug 2018, Dirk Eddelbuettel wrote:
|
| >
| > On 9 August 2018 at 20:37, Tomas Kalibera wrote:
| > | So to answer your original question, this could probably be handled in
| > | Rcpp,
| >
| > Hm. Why do you s
On 15 August 2018 at 20:32, Benjamin Tyner wrote:
| Thanks for the replies and for confirming my suspicion.
|
| Interestingly, src/include/S.h uses a trick:
|
| #define longint int
|
| and so does the nlme package (within src/init.c).
As Bill Dunlap already told you, this is a) ancient an
On 25 August 2018 at 08:26, Hadley Wickham wrote:
| Would someone mind pointing to me to the inspiration for the use of
| the L suffix to mean "integer"? This is obviously hard to google for,
| and the R language definition
| (https://cran.r-project.org/doc/manuals/r-release/R-lang.html#Constant
On 25 August 2018 at 09:28, Carl Boettiger wrote:
| I always thought it meant "Long" (I'm assuming R's integers are long
| integers in C sense (iirrc one can declare 'long x', and it being common to
| refer to integers as "longs" in the same way we use "doubles" to mean
| double precision floati
)
[1] 8
R> Rcpp::evalCpp("sizeof(int)")
[1] 4
R>
Dirk
| H.
|
| On 08/25/2018 10:01 AM, Dirk Eddelbuettel wrote:
| >
| > On 25 August 2018 at 09:28, Carl Boettiger wrote:
| > | I always thought it meant "Long" (I'm assuming R's integers are l
[ Initially posted in r-package-devel, now reposting here by request from
Uwe; my apologies for the cross-post. ]
Package status reports come in three different severities: NOTE, WARNING, and
ERROR. Motivated by Brodie's nice (dependency-free) accessor function for
per-maintainer status [1],
On 17 September 2018 at 07:09, Duncan Murdoch wrote:
| I would not assume that shell behaviour in Windows and Unix would always
| be the same. A better comparison would be to list some other command on
| the same system that behaves differently. For example, on MacOS I see
|
| $ echo 'ls()
|
On 21 September 2018 at 09:50, Steve Grubb wrote:
| Hello,
|
| Top posting. Several people have asked about the code to replicate my
| results. I have cleaned up the code to remove an x/y coordinate bias for
| displaying the results directly on a 640 x 480 VGA adapter. You can find the
| code
Slightly nicer version:
--- snip
#include
// [[Rcpp::export]]
Rcpp::DataFrame stevePlot(Rcpp::NumericVector itable) {
size_t cnt = itable.size(), num = 0;
double nth, n1th = 0, n2th = 0, n3th = 0;
double x, y, usex, use
On 25 September 2018 at 22:59, mikefc wrote:
| Thanks Brodie, that's some nice detective work.
|
| If someone wanted to grant me access to Bugzilla, I'll be happy to post the
| bug and patch there (with your permission Brodie?) and help this bug get
| fixed.
I think it would help your cause if
Robert,
On 3 November 2018 at 10:29, Robert J. Hijmans wrote:
| With the current version of the "raster" package (that I maintain), R CMD
| check on packages "soilDB" and "PopGenReport" have this NOTE:
|
| Package: soilDB
| Check: data for non-ASCII characters
| New result: NOTE
| Error in
I may have a deployment reason at work for Linux binary packages as created
by `R CMD INSTALL --build src`. Using the example of my digest package this
creates eg
digest_0.6.18.1_R_x86_64-pc-linux-gnu.tar.gz
where 'x86_64-pc-linux-gnu' is also what `R.version[["platform"]]` returns.
However
On 6 December 2018 at 15:19, Joris Meys wrote:
| Dear all,
|
| quite a few package tools depend on R CMD INSTALL today for rapid testing
| of a package, eg:
|
| - devtools::install()
| - BiocCheck::BiocCheck()
|
| I've noticed that at least BiocCheck() doesn't ignore version control
| folders
On 6 December 2018 at 15:59, Ralf Stubner wrote:
| On 06.12.18 15:19, Joris Meys wrote:
| > I know this R CMD build ignores these files and folders by default, but R
| > CMD INSTALL doesn't apparently.
|
| to me this is not apparent. I just tried "R CMD INSTALL ." in a package
| directory with a
The short answer, supported (if memory serves) by the R Windows FAQ, is to
_not_ install in a path with spaces in the first place.
Pondering why R on Windows, after all these years, still uses a path with
spaces as the default choice is left as exercise to the reader.
Dirk
--
http://dirk.edde
On 3 January 2019 at 11:43, David Lindelof wrote:
| Dear all,
|
| I’m working as a data scientist in a major tech company. I have been using
| R for almost 20 years now and there’s one issue that’s been bugging me of
| late. I apologize in advance if this has been discussed before.
|
| R has tr
On 7 January 2019 at 22:09, Gergely Daróczi wrote:
| You can provide your app as a Docker image, so that the end-user
| simply calls a "docker pull" and then "docker run" -- that can be done
| from a user-friendly script as well.
| Of course, this requires Docker to be installed, but if that's a
On 1 February 2019 at 13:31, William Dunlap via R-devel wrote:
| To download a package with all its dependencies and install it, use the
| install.packages() functions instead of 'R CMD INSTALL'. E.g., in bash:
|
| mkdir /tmp/libJunk
| env R_LIBS_SITE=libJunk R --quiet -e 'if
| (!requireNamespa
On 25 February 2019 at 18:25, robin hankin wrote:
| Hi there, ubuntu 18.04.2, trying to compile R-devel 3.6.0, svn 76155.
|
| I am having difficulty compiling R. I think I have pcre installed correctly:
|
| OK~/Downloads/R-devel pcretest -C
| PCRE version 8.41 2017-07-05
| Compiled with
| 8
On 4 April 2019 at 17:28, ivo welch wrote:
| The following program is whittled down from a much larger program that
| always works on Intel, and always works on AMD's threadripper with
| lapply but not mclappy. With mclapply on AMD, all processes go into
| "suspend" mode and the program then han
If you are on Debian and want to help test the upcoming R 3.6.0 releases
coming out April 26, I just put a set of packages based on last night's
tarball into Debian's "experimental" branch.
I plan to follow up with at least one beta and rc build each, and at least
one of those will go to the nor
On 5 May 2019 at 10:47, Andrew Janke wrote:
| I'm interested in porting the R example datasets package to GNU Octave
| and Matlab. Would you have objections to my doing so?
You don't even have to ask...
[...]
| Since R's datasets package is GPL, I think I'd be within my rights to
| just do thi
On 7 May 2019 at 19:43, Peter Langfelder wrote:
| (CCing the R-devel list, maybe someone will have a better answer.)
|
| To be honest, I don't know how to. I wasn't able to configure R to use
| OpenBLAS using the configure script and options on my Linux Fedora system.
| I configure it without ex
On 14 May 2019 at 21:44, yueli wrote:
| I downloaded R-3.6.0.tar.gz from https://cran.r-project.org/src/base/R-3/.
|
|
| I tried to install R-3.6.0.tar.gz in Ubuntu system.
You are likely better off to use fully-built and generally
correctly-configured R binary for Ubuntu off the CRAN mirrors.
On 13 June 2019 at 16:05, lejeczek via R-devel wrote:
| I'd like to ask, and I believe this place here should be best as who can
| know better, if building R with different compilers and opt flags is
| something worth investing time into?
|
| Or maybe this a subject that somebody has already inv
On 14 June 2019 at 15:22, arnaud gaboury wrote:
| I have build R with Intel MKL.The libraries are free for one year (maybe
| did it change). The build is far from being trivial. Please find on my
| github[0] some details
Gee, when oh when does this "meme" of "I built R with MKL" die?
BLAS/LAPAC
There seems to be another outage of the Vienna CRAN server [1] though from
what I can from afar not related to DNS outage [2].
Could anyone confirm and possibly alert the local team in Vienna?
Dirk
[1] https://twitter.com/d_olivaw/status/1147161883797086214
[2] The DNS resolves on a few sites
On 14 July 2019 at 13:08, Spencer Graves wrote:
| for that. I lost the history in doing so, but I can live without that
| history.
Well many of us imported svn repos into git repos. And my favourite example
is still ESS as it has history back to 1997 (!!) thanks to cvs2svn
pre-filling its svn
On 15 July 2019 at 11:41, Spencer Graves wrote:
| On 2019-07-15 10:56, Dirk Eddelbuettel wrote:
| >
| > Don't write passwords down like this. Your error is likely in expecting
_ssh_
| > authentication over _https_ -- when it works only over ssh. Use the
alternate
| > form for
On 2 August 2019 at 16:23, Sun Yijiang wrote:
| The R script I run daily for hours looks like this:
|
| while (!finish) {
| Sys.sleep(0.1)
| time = as.integer(format(Sys.time(), "%H%M")) # always crash here
| if (new.data.timestamp() <= time)
| next
| # ... do some jobs f
Roger,
On 4 August 2019 at 06:48, Koenker, Roger W wrote:
| I’d like to solicit some advice on a debugging problem I have in the quantreg
package.
| Kurt and Brian have reported to me that on Debian machines with gfortran 9
|
| library(quantreg)
| f = summary(rq(foodexp ~ income, data = engel,
On 26 July 2019 at 08:48, Robert B. Gramacy wrote:
| That does the trick, thanks! In fact, I had those lines commented out in
| my Rmkl startup script but I can't remember why, since they're part of
| Intel's instructions. Strange that things still worked for somewhat older
| Rs. (Perhaps that
Hi Kasper,
On 6 August 2019 at 10:33, Kasper Daniel Hansen wrote:
| Thanks for the blog post on this, and the pointers in this email.
My pleasure! There wasn't much in there that was "new" but it often helps to
just tie it together with a valid and real example (as provided by Roger).
| I ha
On 6 August 2019 at 10:51, Dirk Eddelbuettel wrote:
| then providing compatibility with what came after. As for Fortran, can't
| recall such a change.
Come to think about it we had it in Debian once or twice in the 20+ years I
contributed but I can't recall anymore when it was eit
Lluís,
You sent a 8+ mb file to a (I presume) 1000+ subscribers of this list. That
is not generally a good idea, and I am surprised this got past the mailman
software which (usually) filters at 100k (and for a reason).
In the future, please consider uploading the file somewhere (GitHub gists ar
On 12 August 2019 at 12:56, Wang Jiefei wrote:
| I am stuck here. I do not know if it is a bug of my package or testthat or
| the ALTREP implementation of R or possibly the interaction between them.
I don't have any concrete advice for your issue here but when I find myself
in similar debugging
Adam,
This can indeed be very frustrating. But depending on the choices you make
it does not have to be that way. Most Linux distributions have 'something'
it may not be comprehensive or current. So most of the time you need to be
able to compile from source. Which is not that hard, and can be
Adam,
Apologies for typos in previous email -- and follow-ups should probably go to
the r-sig-debian list which support R on .deb based distros. I am not sure
have readers from the derivative distro you use, but there is a fairly wide
spread of users there beyond "just" Debian or Ubuntu. Subscri
Joshua,
Doing this well "horizontally" (across different OSs even though for just one
domain, like CRAN and R) is difficult.
We have decent "vertical" solutions (with one OS / distro) for (at least
some) use / deployment cases as I show in a brief blog post and video here
http://dirk.eddelbu
On 24 November 2019 at 22:24, Saren Tasciyan wrote:
| Yes I am aware of it.
So why not use them?
| And yes, I have libicu60 installed. Is it the configure script making a
| mistake?
Err, no. The configure setup is as solid as they come. But as Peter already
said: "have lib$FOO installed" of
On 21 November 2019 at 17:57, Martin Maechler wrote:
| (if you use a version of R-devel, with svn rev >= 77446; which
| you may get as a binary for Windows in about one day; everyone
| else needs to compile for the sources .. or wait a bit, maybe
| also not much longer than one day, for a dock
On 29 December 2019 at 16:39, steven pav wrote:
| One of my packages is slated to be archived from CRAN due to failures when
| the ATLAS BLAS is used. I am unable to replicate the error on my machine
| under R 3.6.1 using the atlas library from ubuntu (seems to be 3.10.2-9,
| while the good profe
On 8 January 2020 at 10:06, Michael Friendly wrote:
| It used to be the case that when I submitted a package and it gave notes
| or warnings in the CRAN checks, I was required to bump the package
| version before re-submission.
|
| I hope this is no longer the case. I recently submitted a pac
lille stor,
As a general rule, please do not cross-post.
And almost certainly do not simultaneously as you did here and on
https://stackoverflow.com/questions/59663174/get-memory-address-of-an-r-data-frame
Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
__
On 13 January 2020 at 10:02, Therneau, Terry M., Ph.D. via R-devel wrote:
| Where can I find out (and replicate) what options as-cran turns on?
See the file src/library/tools/R/check.R in the R sources, and grep for
as_cran which is the internal variable controlled by the --as-cran option
[...]
On 13 January 2020 at 14:51, Therneau, Terry M., Ph.D. wrote:
| 3. Dirk gave good input about the flags in R CMD check and how to find them.
One more
| line in the "Writing R Extensions" manual would have been helpful, namely
that many of the
| options are NOT available in the options() com
Hi Serguei,
Nice analysis!
On 14 January 2020 at 11:00, Serguei Sokol wrote:
| During my recent r2sundials development, I've came across a strange test
| failing during 'R CMD check' exclusively on win R-devel which I could
| reproduce with a minimal example that I present here.
| The toy pac
On 15 January 2020 at 09:29, Abby Spurdle wrote:
| Recently, I tried to install R on Fedora.
| However, it only gave me the option of downloading and installing R
| 3.6.1, when the current release is/was R 3.6.2.
| I decided to wait, and may try again later, over the next week.
|
| Is it possibl
Charles,
Did you try a build of the provided alpha, beta and rc releases made
available to allow you to ensure that the released version would build and
perform as expected?
FWIW the new 3.6.3 made ~ 12 hours ago are already available for Debian,
built for the Ubuntu backports at CRAN (thanks t
On 13 March 2020 at 20:26, Greg Minshall wrote:
| hi. i'd like to instantiate sed(1), send it some input, and retrieve
| its output, all via pipes (rather than an intermediate file).
|
| my sense from pipe and looking at the sources (sys-unix.c) is that is
| not possible. is that true? are th
On 18 March 2020 at 19:19, Henrik Bengtsson wrote:
| AFAIU, 'R CMD check --as-cran' tries to hide any site and user package
| libraries by setting R_LIBS_SITE and R_LIBS_USER. However, contrary
What makes you think that? AFAIK --as-cran just sets a bunch of the (nearly
countless) environment va
On 23 March 2020 at 17:07, Ben Bolker wrote:
| Or is there a way I can use Shield() since this an Rcpp-based project
| anyway?
Yes you can, and I would recommend it.
Example from Rcpp itself, file Environment.h:
Shield res(Rcpp_fast_eval(Rf_lang2(asEnvironmentSym, x), R_GlobalEnv));
For Rc
On 24 March 2020 at 11:39, Lionel Henry wrote:
| > Shield res(Rcpp_fast_eval(Rf_lang2(asEnvironmentSym, x),
R_GlobalEnv));
|
| The call should be protected before evaluation though. So more like:
|
| Shield call(Rf_lang2(asEnvironmentSym, x));
| return Rcpp_fast_eval(call, R_GlobalEnv);
Good
On 24 March 2020 at 07:19, Dirk Eddelbuettel wrote:
| On 24 March 2020 at 11:39, Lionel Henry wrote:
| | > Shield res(Rcpp_fast_eval(Rf_lang2(asEnvironmentSym, x),
R_GlobalEnv));
| |
| | The call should be protected before evaluation though. So more like:
| |
| | Shield call(Rf_la
There appears to have been some progress on this matter:
-Note that @command{g++} 4.9.x (as used for @R{} on Windows up to 3.6.x)
+Note that @command{g++} 4.9.x (as used on Windows prior to @R{} 4.0.0)
See SVN commit r78169 titled 'anticipate change in Windows toolchain', or the
mirrored git co
Or you use a fourth component to signal a development version as Rcpp has
done for years (and, IIRC, for longer than devtools et al used '9000').
There is no functional difference between 1.2.3.1 and 1.2.3.9000. They are
both larger than 1.2.3 (in the package_version() sense) and signal an
inter
Jitao,
Thanks for writing this up.
You could add a section on 'prior art' and references. The canonical example
always was (c.f. Writing R Extensions)
lme4 <-> Matrix
which was followed early by the CRAN packages
zoo <-> xts
upon which I built
xts <-> RcppXts
with a write-up (f
Spencer,
On 17 April 2020 at 09:14, Spencer Graves wrote:
| How can someone help me find and fix the following, contained in
| 00check.log on Debian for "https://github.com/JamesRamsay5/fda":
|
| NOTE
| Found the following files/directories:
| ‘fdaMatlabPath.m’
| * checking for detri
1 - 100 of 967 matches
Mail list logo
