1FLAGS found, something is wrong.FALSE
The strange (to me) thing is that the package is 100% R, so I don't
understand why C compiler flags are even in play. Earlier versions
worked as expected under both Linux and Windows.
Any hints?
Thanks!
--
Steve Gutreuter
_
Thank you!!!
On 12/9/21 11:16 AM, Uwe Ligges wrote:
On 09.12.2021 17:10, Steve Gutreuter wrote:
I am getting the following warnings from devtools:check():
W checking whether package ‘screenr’ can be installed (4.8s)
Found the following significant warnings:
Warning: replacing
warnings were triggered. I have searched my code for instances of
*cov, *var and *smooth and found nothing. I suspect that the warnings
are coming from functions from the stats package.
Any hints about how to trace those warnings or, better yet, overcome
them will me much appreciated
--
Steve
6#diff-bc92b187c74649b3e0a039784ff93b39
>
> Undo the `#*` line.
>
> Gabor
>
> On Tue, Oct 1, 2019 at 2:26 PM Steve Gutreuter wrote:
>> First, thank you Bill Dunlap, Peter Dalgaard and Max Turgeon,
>>
>> I edited (incompletely) the initial posting and failed to change screenr
>> to my
On 9/30/19 5:30 PM, William Dunlap wrote:
> Will the package build if you back out the "minor changes"? If so,
> what were the minor changes (show diff output)?
>
> Bill Dunlap
> TIBCO Software
> wdunlap tibco.com <http://tibco.com>
>
>
> On Mo
I have a package which will no longer build after minor changes. The
problem occurs under both Windows 10 and Linux Mint. For example, from a
Windows terminal I do:
C:\Users\xyz\OneDrive - ORG\Computing\Devel> R CMD build screenr
and I get:
* checking for file 'mypackage/DESCRIPTION' ... OK
*
