Hi,
thanks everyone for the input, I now have a few more leads to follow.
It would be great to have a general single package builder
even for existing packages to check if one has no direct access
to the failing architecture.
https://win-builder.r-project.org/ is discouraging BioC package upl
I second the idea of reproducing with the Windows build commands, which have to
do more than 'just' build for a particular architecture. One might test the
hypothesis that it is staged install that is causing the problem with
StagedInstalll: no
in the DESCRIPTION file.
Makevars is evaluated
I can reproduce the error using R-3.6.0beta and running the following two
steps to replicate the Bioc builder commands:
R CMD build --keep-empty-dirs --no-resave-data Rdisop
rm -rf Rdisop.buildbin-libdir && mkdir Rdisop.buildbin-libdir &&
C:\Users\biocbuild\bbs-3.9-bioc\R\bin\R.exe CMD INSTALL --m
Hi,
with the next release coming up, I am out of wits regarding the failure at
http://bioconductor.org/checkResults/devel/bioc-LATEST/Rdisop/tokay2-buildbin.html
which exists since before April this year, when we committed
some changes to get rid of the RcppClassic dependency.
Max Helf succeede
