Message-ID: <54595506.7000706@gmail.com>
Date: 2014-11-04T22:36:54Z
From: kaveh
Subject: Linking to the BH package introduces CRAN warnings
In-Reply-To: <CABdHhvEiGiXAYymj4Fw2BTMw7Jq+BHBu0q=CR6kCRXYFph2VKw@mail.gmail.com>
Dear Hadley,
Thank you for this information, maybe the CRAN gods
will look favourably on this case too,
Best regards,
On 2014-11-04 23:32, Hadley Wickham wrote:
>>> | However, it seems some of the codes in the BH package
>>> | might. At any rate, when I include some boost headers such as
>>> | boost/math/distributions/ through BH, I get the following warnings
>>> | when submitting to the win-builder page:
>>> |
>>> |
>>> | Found '_ZSt4cerr', possibly from 'std::cerr' (C++)
>>> |
>>> | Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
>>> |
>>> | Found '_ZSt4cerr', possibly from 'std::cerr' (C++)
>>> |
>>> | Found 'abort', possibly from 'abort' (C), 'runtime' (Fortran)
>> You?re kind of out of luck. These functions are both:
>> - used by the boost headers
>> - forbidden by R, well at least forbidden by CRAN
> Maaaaybe - I had this note in RSQLite, and CRAN seemed ok with my explanation:
>
> * checking compiled code ... NOTE
> File ?/Users/hadley/Documents/databases/RSQLite.Rcheck/RSQLite/libs/RSQLite.so?:
> Found ?___stderrp?, possibly from ?stderr? (C)
> Object: ?sqlite-all.o?
>
> This is in C code from the embedded SQLite database.
>
>
> Hadley
>