Hi Dario,
Gabe is right, you shouldn't be building within the package directory.
Although AFAIK, you should be able to do so. Perhaps if you point us
to your package, we might be able to see the issue...
Regards,
Marcel
On 03/21/2018 06:15 PM, Gabe Becker wrote:
Dario,
Does this ever
Dario,
Does this ever happen if you build in the parent directory? I don't think
building within the package directory is best practice and I'm not sure
it's (officially) supported at all. The error message seems to support that.
~G
On Wed, Mar 21, 2018 at 9:40 AM, Dario Righelli
Hi,
I've a package with a DESCRIPTION file inside of it, as usual.
It's a couple of times that, when I try to build the package on my local
machine or on travis-ci, I get this error:
Building package
Building with: R CMD build
0.74s$ R CMD build .
* checking for file ‘./DESCRIPTION’ ... OK
*
Thanks guys for your kind help! I would follow your tips and try to fix
these issues.
It's indeed quite hard to maintain it, luckily in past two years I made it.
It's indeed the right time to cut down some unnecessary packages and make
it easier to be maintained.
Thanks for your help! ^_^
Best
Hi,
On 03/21/2018 07:32 AM, Martin Morgan wrote:
On 03/21/2018 10:14 AM, Henrik Bengtsson wrote:
A few quick comments:
* I don't think the limit was hardened in R 3.4.0; maybe you started to
experience it sound then because more dependent packages started to
rely on
more DLLs?
* The
On 03/21/2018 10:14 AM, Henrik Bengtsson wrote:
A few quick comments:
* I don't think the limit was hardened in R 3.4.0; maybe you started to
experience it sound then because more dependent packages started to rely on
more DLLs?
* The limit is OS/platform specific so it's not that R core is
Hello Guys:
I encountered an error like "maximal number of dlls reached...". I am
maintaining ChAMP package now, which integrated many other packages in my
research field. I have not updated this package in past 2 months but
suddenly this error happens.
Currently, I think I know the reason is
Thanks Marcel, it works!
After clearing the cache (Wercker > Project > Options > Cache > "Clear
cache" button), R CMD check now works perfectly on Wercker.
Indeed, I think I initially used an older box, and didn't realise that the
cached box was being fetched instead of downloading the more
