I am using #pragma omp statements all over the place and this is the only
type causing crashes. I'm guessing it has something to do with travis
building on a 12.04 ubuntu VM with a rather old gcc (4.6.3).
2. Is there a workaround, or should I just go for another build service
(which one)?
Yo
ming at changing upstream sources as little as
possible)?
--
Ege Rubak, Associate Professor,
Department of Mathematical Sciences, Aalborg University
Fredrik Bajers Vej 7G, 9220 Aalborg East, Denmark
Phone: (+45)99408861
Mobile: (+45)30230252
Email: ru...@math.aau.dk
___
The main things seem to be related to (travis log is at
https://travis-ci.org/spatstat/s2/jobs/149578339):
1. Deprecated C++ headers and .
2. Compiled code that calls entry points which might terminate R or
write to stdout/stderr.
Is it hopeless to get on CRAN with warnings like these?
I d
Thanks for the good specific suggestions Kevin and Max. It is amazing
that great help is available from the R community in such a short time.
Clearly everybody thinks that these issues should be fixed before I even
try to submit to CRAN (and I fully agree that they shouldn't lower their
standa
On 08/10/2016 04:05 PM, Dirk Eddelbuettel wrote:
On 10 August 2016 at 08:39, Charles Determan wrote:
| I have seen this previous discussion (
| https://stat.ethz.ch/pipermail/r-package-devel/2015q2/000115.html) on this
| question but I didn't find a clear answer. I am looking at integrating
|
A quick search on METACRAN on GitHub gives quite a few results:
https://github.com/search?q=org%3Acran+rwarn&type=Code
The first couple of package hits:
rodeo
rootSolve
geoBayes
Good luck!
/Ege
On 02/16/2017 10:22 AM, Avraham Adler wrote:
Hello.
Would anyone know of a package which uses the r
Hi,
This is something that has gotten quite a bit of attention recently due
to the coming R 3.4 giving a NOTE when routines aren't declared. You
should be able to find info on this list or elsewhere.
Basically you need to make a file called e.g. init.c in your src/ with
the appropriate code. T
ndable to install the rhub
package.
Alternatively, submitting to http://win-builder.r-project.org/ also lets
you test under R-devel.
Best,
Ege
Best,
Zhian
Regards,
Vineetha Warriyar
From: R-package-devel mailto:r-package-devel-boun...@r-project.org>>
Hi,
We had this issue with `median.im` in spatstat. I wasn't involved in
fixing it, but maintainer Adrian Baddeley changed the documentation
according to CRAN instructions. You can see it here:
https://github.com/spatstat/spatstat/blob/master/man/mean.im.Rd
Maybe you can use that for inspiratio
Hello,
Maybe you could start by writing a polite email to Paul Murrell (the
maintainer of `gridGraphics` according to
https://cran.r-project.org/package=gridGraphics) and ask if he is aware
that his package fails on OSX on CRAN.
If you are lucky he might be able to quickly fix the issue and
nally do this in the Makevars file
if the strip tool is available (typically the case on Linux). Does
anybody know what CRAN's take is on this?
Cheers,
Ege
[1]:
http://dirk.eddelbuettel.com/blog/2017/08/14/#009_compact_shared_libraries
--
Ege Rubak, Associate Professor,
Department of Ma
Hi Rolf,
Another place to look for macros in Rd files would be in the spatstat
package which I know you are quite familiary with ;-)
However, I think our macros are plain LaTeX without calls to \Sexpr so
it may behave differently than the case at hand.
Cheers,
Ege
On 11/10/2017 02:00 AM, Rolf
The obvious place to look for pointers of how to detect and link
correctly to fftw would be in the current CRAN package `fftwtools` that
does it without any Rcpp:
https://github.com/krahim/fftwtools
Cheers,
Ege
On 11/28/2017 02:47 AM, Dirk Eddelbuettel wrote:
On 27 November 2017 at 21:24, T
This in not well thought through, but what about using `sink` to capture
any messages from the call? Then you might be able to remove the
expected warning and output any remaining warnings if they are there...
However, note this part of `help(sink)`:
Sink-ing the messages stream should be done
Hi,
It may be a big task to ship all of GSL with your R package, and since
it is a large standard library which is "easy" to install on most
systems, I doubt that it's worth the effort. I would recommend putting
`GSL (>=2.3)` in `SystemRequirements` in your DESCRIPTION file.
As you point out
On 27/11/2019 00.22, Fernando Roa wrote:
- I used a guest debian 10 in vmware in my system, and couldn't replicate
the error installing with R CMD INSTALL
I guess you should rather run "R CMD check ..." on the tar.gz file to
reproduce the error.
Hope that helps.
/Ege
_
Hi all,
My two cents are below Marc's summary here:
On Thu, 2020-10-22 at 20:33 -0400, Marc Schwartz wrote:
> Right now, the interpretation, without further clarification from
> CRAN, would be, it is ok for a package to be on CRAN with license
> based usage restrictions included (e.g. for non-com
at 2.0-1 is available from this repository they may pass
the incoming checks on CRAN, but my hopes are not too high.
If this was successful the reverse dependencies would be compatible
with spatstat 2.0 and on CRAN and so spatstat 2.0 would break nothing
and we could resubmit.
Best regards
rts them. This way it
> could
> be done with no breaking changes. Reverse dependencies could change
> to
> depend on spatstat. at their leisure.
>
> Duncan Murdoch
>
> On 11/03/2021 10:18 a.m., Ege Rubak wrote:
> > Dear all,
> >
> > I'm seeking
s?
> Maybe there's a way to make the new packages compatible with the old
> one, so there would be no excuse for the downstream packages not to
> update right away.
>
> Duncan Murdoch
>
>
> On 11/03/2021 7:39 p.m., Ege Rubak wrote:
> > Dear Duncan,
> >
20 matches
Mail list logo
