For what it's worth, the package compiles successfully on my own macOS
machine but it takes a long time to build just because of how large it is.
Perhaps the CRAN build machine is set to interrupt long-running
installations, under the assumption that they're hanging / frozen?
Given how many C++ so
Thanks Uwe. Will do.
On Tue, Jun 5, 2018 at 1:55 PM, Uwe Ligges
wrote:
> Please ask the Mac maintainer, Simon Urbanek, in such a case where it is
> not obvious what is going on.
>
> Best,
> Uwe Ligges
>
>
>
>
>
> On 05.06.2018 18:45, Steven Scott wrote:
>
>> If there's anyone willing to take a
Please ask the Mac maintainer, Simon Urbanek, in such a case where it is
not obvious what is going on.
Best,
Uwe Ligges
On 05.06.2018 18:45, Steven Scott wrote:
If there's anyone willing to take a look at the build errors I would
appreciate it. I'm trying to work a bug report from a downst
This seems like a nice solution -- the only disadvantages I can think
of are (1) extra hassle (2) it might generate messages about function
masking when the upstream package (e.g. broom) is loaded?
On 2018-05-25 12:00 PM, Neal Fultz wrote:
> In the estimatr package, we provided a shim to suppo
If there's anyone willing to take a look at the build errors I would
appreciate it. I'm trying to work a bug report from a downstream user, and
I think the OSX build has an issue that I don't understand.
Thanks.
On Thu, May 31, 2018 at 1:49 PM, Steven Scott
wrote:
> Looking at the Boom package
