Displaying 5 results from an estimated 5 matches for "yet_".
Did you mean:
yet
2019 May 10
2
R 3.6.0 for Debian buster
...tween gcc/gfortran upstream and the lapack folks. See Tomas's
> posts on (IIRC) r-devel.
> So in short, things are moving, and in the right direction. Also worth
> recalling that the _initial findings_ were and still are about a gcc /
> gfortran version _not even in Debian unstable yet_ (but the folks in
> Fedora once again jumped the gun and they now have that problem with
> gfortran 9).
Afaics, the issue certainly affects current gfortran-8 in testing?
-k
2019 May 10
2
R 3.6.0 for Debian buster
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
2019 May 10
0
R 3.6.0 for Debian buster
...s and
is now also between gcc/gfortran upstream and the lapack folks. See Tomas's
posts on (IIRC) r-devel.
So in short, things are moving, and in the right direction. Also worth
recalling that the _initial findings_ were and still are about a gcc /
gfortran version _not even in Debian unstable yet_ (but the folks in Fedora
once again jumped the gun and they now have that problem with gfortran 9).
Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org
2019 May 10
0
R 3.6.0 for Debian buster
...gfortran upstream and the lapack folks. See Tomas's
| > posts on (IIRC) r-devel.
|
| > So in short, things are moving, and in the right direction. Also worth
| > recalling that the _initial findings_ were and still are about a gcc /
| > gfortran version _not even in Debian unstable yet_ (but the folks in
| > Fedora once again jumped the gun and they now have that problem with
| > gfortran 9).
|
| Afaics, the issue certainly affects current gfortran-8 in testing?
Correct -- my bad. As Debian pulled that upstream patch in. In any event I
was planning to push an updated r-bas...
2019 May 10
2
R 3.6.0 for Debian buster
...lapack folks. See Tomas's
> | > posts on (IIRC) r-devel.
> |
> | > So in short, things are moving, and in the right direction. Also worth
> | > recalling that the _initial findings_ were and still are about a gcc /
> | > gfortran version _not even in Debian unstable yet_ (but the folks in
> | > Fedora once again jumped the gun and they now have that problem with
> | > gfortran 9).
> |
> | Afaics, the issue certainly affects current gfortran-8 in testing?
> Correct -- my bad. As Debian pulled that upstream patch in. In any
> event I was pla...