similar to: R 3.6.0 for Debian buster

Am Montag, 29. April 2019, 13:44:03 CEST schrieb Kurt Hornik: > >>>>> Johannes Ranke writes: > Thanks. You may have seen that with current gfortran in > testing/unstable, there are problems with the R BLAS/LAPACK API entries > using a Fortran interface (and hence in particular when using the BLAS > and LAPACK sources that ship with R). No, I wasn't aware of

Am Montag, 29. April 2019, 15:03:54 CEST schrieb Kurt Hornik: > >>>>> Johannes Ranke writes: > > Am Montag, 29. April 2019, 13:44:03 CEST schrieb Kurt Hornik: > >> >>>>> Johannes Ranke writes: > >> Thanks. You may have seen that with current gfortran in > >> testing/unstable, there are problems with the R BLAS/LAPACK API entries

On 29 April 2019 at 15:03, Kurt Hornik wrote: | >>>>> Johannes Ranke writes: | | > Am Montag, 29. April 2019, 13:44:03 CEST schrieb Kurt Hornik: | >> >>>>> Johannes Ranke writes: | >> Thanks. You may have seen that with current gfortran in | >> testing/unstable, there are problems with the R BLAS/LAPACK API entries | >> using a Fortran

Kurt, Am Donnerstag, 9. Mai 2019, 16:35:24 CEST schrieb Kurt Hornik: > >>>>> Johannes Ranke writes: > Johannes, > > It seems that one can avoid the gfortran problems with Fortran > BLAS/LAPACK implementations by compiling with > -fno-optimize-sibling-calls. ... > Yesterday I changed R-devel and R-patched to use > -fno-optimize-sibling-calls for gfortran

>>>>> Johannes Ranke writes: > Am Montag, 29. April 2019, 13:44:03 CEST schrieb Kurt Hornik: >> >>>>> Johannes Ranke writes: >> Thanks. You may have seen that with current gfortran in >> testing/unstable, there are problems with the R BLAS/LAPACK API entries >> using a Fortran interface (and hence in particular when using the BLAS >>

>>>>> Johannes Ranke writes: Thanks. You may have seen that with current gfortran in testing/unstable, there are problems with the R BLAS/LAPACK API entries using a Fortran interface (and hence in particular when using the BLAS and LAPACK sources that ship with R). It seems I can avoid these using OpenBLAS (but then this really only works find for me provided I setenv

>>>>> Dirk Eddelbuettel writes: > On 10 May 2019 at 13:46, Kurt Hornik wrote: > | >>>>> Dirk Eddelbuettel writes: > | > | > On 10 May 2019 at 10:52, Johannes Ranke wrote: > | > | Thanks, that sounds good. But I need some help as I do not know much about > | > | autoconf and Debian packaging: Is it enough to patch configure.ac (r76467) or

>>>>> Johannes Ranke writes: Johannes, It seems that one can avoid the gfortran problems with Fortran BLAS/LAPACK implementations by compiling with -fno-optimize-sibling-calls. Tomas recently wrote to R Core that ********************************************************************* - gfortran is leaning to (but no official announcement decision has already been reached)

On 9 May 2019 at 16:35, Kurt Hornik wrote: | >>>>> Johannes Ranke writes: | | Johannes, | | It seems that one can avoid the gfortran problems with Fortran | BLAS/LAPACK implementations by compiling with | -fno-optimize-sibling-calls. | | Tomas recently wrote to R Core that | | ********************************************************************* | - gfortran is leaning to

>>>>> Dirk Eddelbuettel writes: > On 10 May 2019 at 10:52, Johannes Ranke wrote: > | Thanks, that sounds good. But I need some help as I do not know much about > | autoconf and Debian packaging: Is it enough to patch configure.ac (r76467) or > | do we need to update configure as well (r76468)? > Again, that would happen in the sources you pick up from me, and per

What is the correct way to globally configure R to default to single (or at least, << NUM_CPUS) threaded operation? Using R 3.3.1 (both in debian unstable or using the CRAN repository for xenial) with OpenBLAS (0.2.18) defaults to using one thread per available CPU, which isn't ideal for machines more than a couple of CPUs. Setting the environment (OMP_NUM_THREADS or

Hi, I was be half asleep in the heat ... 2016-08-04 0:04 GMT+09:00 Dirk Eddelbuettel <edd at debian.org>: > > On 3 August 2016 at 16:45, Gordon Ball wrote: > | On 02/08/16 03:10, Ei-ji Nakama wrote: > | > Hi, > | > > | > Create /etc/profile.d/openblas.sh. > | > Write the following during in this file. > | > OPENBLAS_NUM_THREADS = 1 > | > export

Dear All, Here is my reproducible example: > library(stargazer) Please cite as: Hlavac, Marek (2018). stargazer: Well-Formatted Regression and Summary Statistics Tables. R package version 5.2.2. https://CRAN.R-project.org/package=stargazer > x1=1:1000 ; y = 2 * x1+ rnorm(1000) > stargazer(lm(y~x1)) Error in (.format.s.statistics.list != "p25") &&

On 02/08/16 03:10, Ei-ji Nakama wrote: > Hi, > > Create /etc/profile.d/openblas.sh. > Write the following during in this file. > OPENBLAS_NUM_THREADS = 1 > export OPENBLAS_NUM_THREADS > > OPENBLAS_NUM_THREADS environment variable does not affect the OMP_NUM_THREADS. > Thanks for the response. This works fine for R run from the command line (as does setting the same

On 5 June 2020 at 08:52, Johannes Ranke wrote: | Hi Mark, | | Am Freitag, 5. Juni 2020, 00:31:34 CEST schrieb Mark van der Loo: | > Hi all, | > | > I just spun up a fresh Debian Buster instance, then I added: | > | > deb http://cloud.r-project.org/bin/linux/debian buster-cran40/ | > | > to /etc/apt/sources.list. I also ran the apt-key command as described here: | >

Dear All, I had done an automatic upgrade of my Debian 10 system which had also upgraded R. I reinstalled the stargazer package and the error went away. Query : Do I need to reinstall all packages with each upgrade of R ? Best, Ashim On Thu, Jun 8, 2023 at 11:11?AM Ashim Kapoor <ashimkapoor at gmail.com> wrote: > > Dear All, > > Here is my reproducible example: > >

Has anyone succeeded in getting a parallel BLAS, such as Goto's BLAS, installed on a machine running Ubuntu 11.10? I currently have the libatlas3gf-base package installed on a machine with an AMD Athlon X4 processor. I tried to install the libopenblas-base and libopenblas-dev packages but there seemed to be a glich related to having both libopenblas and libatlas3gf installed so that when I

Hi Lorenzo, On Sun, Jul 7, 2019 at 6:42 AM Lorenzo Isella <lorenzo.isella at gmail.com> wrote: > > Dear All, > I have just upgraded to Debian stable 10 and rebuilt most of the R > packages. > I use the R backported packages from here > > https://cran.r-project.org/bin/linux/debian/#debian-buster-testing > > for the core system. > I encounter some issues when

On Thu, 08 Jun 2023, Ashim Kapoor writes: > Dear All, > > I had done an automatic upgrade of my Debian 10 system which had also > upgraded R. > > I reinstalled the stargazer package and the error went away. > > Query : Do I need to reinstall all packages with each upgrade of R ? > > Best, > Ashim Your session info says "stargazer 5.2.2". What version

Hi all, I just spun up a fresh Debian Buster instance, then I added: deb http://cloud.r-project.org/bin/linux/debian buster-cran40/ to /etc/apt/sources.list. I also ran the apt-key command as described here: https://cran.r-project.org/bin/linux/debian/#secure-apt So far so good, now when I do the following, I get no joy: $ sudo apt-get install r-base Reading package lists... Done Building