Kurt Hornik submitted a bug report to the gfortran maintainers yesterday, and
yes, it seems to have a lot to do with this.
He and Brian Ripley have been able to pinpoint it to certain gfortran revisions
(specifically gfortran-9 at least r268992, or gfortran-8 at least r269349), but
we're lackin
On 18.04.19 07:53, Benjamin Christoffersen wrote:
>> In short, you need to look more closely.
> Is there a way to tell which BLAS and LAPACK is used on the Debian
> machines on CRAN?
I am sure CRAN machines use BLAS and LAPACK as shipped with R, i.e. not
*any* variant of system BLAS/LAPACK.
cheer
Benjamin, did you try with rhub? Gábor makes a great effort there to
keep it up to date with CRAN machines. And even if you still are not
able to reproduce it with the current config, you could try to modify
the docker file yourself.
Iñaki
On Thu, 18 Apr 2019 at 07:53, Benjamin Christoffersen
wr
Thanks for the quick reply. First a correction. I meant Ubuntu 18.04.2
of course, sorry.
> In short, you need to look more closely.
Is there a way to tell which BLAS and LAPACK is used on the Debian
machines on CRAN? I checked the "CRAN Package Check Flavors" page but
there is no information there
On 17 April 2019 at 11:06, Benjamin Christoffersen wrote:
| Since the start of April, I have gotten some errors on the Debian
| machines on the check on CRAN for my package dynamichazard. The places
| where I get the errors seems to come down to LAPACK's dtrtri routine.
| I have tried to reproduc
Dear Sirs,
Since the start of April, I have gotten some errors on the Debian
machines on the check on CRAN for my package dynamichazard. The places
where I get the errors seems to come down to LAPACK's dtrtri routine.
I have tried to reproduce the error on Debian 18.04.2 with clang 8.0.0
but I can
