> Anyway, it is great to have the extra flag. I just prepared r-base 3.6.0-2
> and it contains the new flag in /etc/R/Makeconf thanks to your changes to
> configure{,.ac} which I "backported" to 3.6.0-2. It also includes the
> whitelist for the non-portable compiler flags noise.
Great! I just
On 10 May 2019 at 18:31, Kurt Hornik wrote:
| Thanks. Btw, Tomas just told R Core that
|
| *
| I had a quick look at reference lapack builds in different
| distributions: looking at the disassembly, and specifically for dposv
> 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:
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)
> 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
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
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
On 9 May 2019 at 10:07, Dirk Eddelbuettel wrote:
| Kurt, there is one thing that has been bugging me too and I was wondering if
| I could lean on you as I have not had time work it out. It seems that one
| "should" be to set an environment variable to suppress additional
| "non-portable compiler
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
|
|
> 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
*
-
> Dirk Eddelbuettel writes:
> 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
> | >>
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
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
> 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
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
Dear all,
Now that the upcoming Debian release "buster" is frozen, I have started
supplying backports for it. Pending mirror synchronisations, R 3.6.0 is now
available for Debian buster on i386 and amd64 architectures. Please refer to
https://cran.r-project.org/bin/linux/debian/
for
17 matches
Mail list logo
