Thanks so much for looking into this. You were right, my path that I
had been too lazy to update was pointing at an older installation of R
that I had been too lazy to uninstall.
On Wed, Jun 12, 2019 at 6:41 PM Uwe Ligges
wrote:
>
> So this is likely caused by your setup as I simply get
>
> $ R C
Too many layers of complexity for me, can you take the package sources
and zat /or zip) them for me and send them? Then I'll take a look.
Best,
Uwe Ligges
On 12.06.2019 08:23, Rob Foxall wrote:
Thanks. I ran in R:
devtools::build("myPackage")
That gave me a warning:
NB: this package now d
Thanks. I ran in R:
devtools::build("myPackage")
That gave me a warning:
NB: this package now depends on R (>= 3.5.0)
WARNING: Added dependency on R >= 3.5.0 because serialized
objects in serialize/load version 3 cannot be read in older versions
of R.
File(s) containing such objects
Thanks for the replies. I am still stuck, although agree it is most
likely due to change to R version 3.6.0. I did however manage to
create a dummy package that now does re-create the same error, this
required the inclusion of a data object. The R CMD build error occurs
regardless of whether there
You might be able to find where the error occurred by putting the following
lines in ~/.Rprofile
cat("~/.Rprofile: setting alternate error handler\n")
options(
error=quote({
dump.frames()
writeLines(c("Stack trace", paste0(" ",names(last.dump}))
Bill Dunlap
TIBCO Software
On 10 June 2019 at 13:21, Rob Foxall wrote:
| I've got an R package that I periodically create in what I assume is
| an old-fashioned way:
|
| Within R: use "package.skeleton"
| Outside of R: update e.g. .rd files as appropriate
| Command window: run the following commands
| R CMD build packageN
Hi,
(Re-posting here as per advice from r-help)
I've got an R package that I periodically create in what I assume is
an old-fashioned way:
Within R: use "package.skeleton"
Outside of R: update e.g. .rd files as appropriate
Command window: run the following commands
R CMD build packageName
R CMD
