Henrik Bengtsson
2010-Apr-15 06:26 UTC
[Rd] CRAN: MacOS X binary: not available, see check log?
For a couple of days, MacOS X binaries are not build on CRAN (for my recently uploaded packages only?): The R.oo package is listed as "MacOS X binary: not available, see check log?", but the 'check log' show no errors URL: http://cran.r-project.org/web/packages/R.oo/ Is this a known issue? /Henrik
Simon Urbanek
2010-Apr-15 13:45 UTC
[Rd] CRAN: MacOS X binary: not available, see check log?
On Apr 15, 2010, at 2:26 AM, Henrik Bengtsson wrote:> For a couple of days, MacOS X binaries are not build on CRAN (for my > recently uploaded packages only?): >AFAICS your package was posted on Apr 13 so at the earliest it can be built in the Apr 14 run = yesterday. There was no Apr 14 run because the R build failed on Apr 13. I was chasing the subsequent issues yesterday and I think the latest R build is now working so today's package update should be on CRAN soon. Don't forget that packages have to swim across the Atlantic to get built and then back as binaries, so the migration can take a day or two ;). Cheers, Simon> The R.oo package is listed as "MacOS X binary: not available, see > check log?", but the 'check log' show no errors > URL: http://cran.r-project.org/web/packages/R.oo/ > > Is this a known issue? >> /Henrik > > ______________________________________________ > R-devel at r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-devel > >
Apparently Analagous Threads
- Installation problems with R.classes bundle
- [LLVMdev] [llvm-commits] [llvm] r65296 - in /llvm/trunk: include/llvm/CodeGen/ lib/CodeGen/SelectionDAG/ lib/Target/CellSPU/ lib/Target/PowerPC/ lib/Target/X86/ test/CodeGen/X86/
- MacOS X binary for lme4 not available on CRAN
- SUGGESTION: Force install.packages() to use ASCII encoding when parse():ing code?
- R CMD check: unstated dependence on a standard package.