Re: [Rd] r-forge build failure bafflement

2012-03-30 Thread Ben Bolker
On 12-03-30 08:14 PM, Brian G. Peterson wrote: > On my phone, so replying off-list, but wouldn't loading the data > objects in a running R session and using the appropriate > compression arguments to save() do the trick? - Brian I might try that, but I have a strong suspicion that R will try to

Re: [Rd] r-forge build failure bafflement

2012-03-30 Thread Ben Bolker
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Figured it out (I think: I haven't gotten through restructuring and testing, but I think it's going to work now). I was paying insufficient attention to the build arguments, in particular - --resave-data=best. I previously had the clever idea to

Re: [Rd] r-forge build failure bafflement

2012-03-29 Thread Prof Brian Ripley
We've seen similar things several times with CRAN submissions. Basic scenario was - INSTALL (via build or check) is trying to install a package that is not already installed, into a private library not on the usual .libPaths(). - Start-up code in that package is looking for the package, and

Re: [Rd] r-forge build failure bafflement

2012-03-29 Thread Uwe Ligges
On 29.03.2012 22:54, Ben Bolker wrote: I am attempting to build a package on r-forge and running into a weird error. I have been in correspondence with the R-forge admins and am turning to r-devel on the remote chance that someone might have a guess as to what is going wrong or a suggestio

[Rd] r-forge build failure bafflement

2012-03-29 Thread Ben Bolker
I am attempting to build a package on r-forge and running into a weird error. I have been in correspondence with the R-forge admins and am turning to r-devel on the remote chance that someone might have a guess as to what is going wrong or a suggestion about further diagnostics/experiments I co