...or, I suppose, it would seem like Just Bad Luck, (binary package compatibility etc.). I'll update the M4 MacBook after 4.4.3 comes out.
(And also see if I can orchestrate moving the nightly builds to that machine before we start the 4.5.0 process. Not that the source tarballs are very dependent on the platform that builds them, but I like to have the implied build tests reasonably in sync with your binaries.) - pd > On 19 Feb 2025, at 20:00 , Simon Urbanek <simon.urba...@r-project.org> wrote: > > > >> On Feb 20, 2025, at 2:36 AM, peter dalgaard <pda...@gmail.com> wrote: >> >> Do we expect to stay with gfortran 12.2.0 for 4.4.3 and then switch for >> 4.5.0? >> > > Most likely - changing version for patch releases doesn't seem necessary. > > Cheers, > Simon > > >> -pd >> >>> On 19 Feb 2025, at 03:02 , Simon Urbanek <simon.urba...@r-project.org> >>> wrote: >>> >>> >>> Stefano, >>> >>> please note that the CRAN page is talking about the R 4.4.2 release and the >>> developer tools page says >>> >>> "CRAN R Big Sur builds used gfortran-12.2-universal.pkg for R 4.3.0 up to >>> 4.4.2" >>> >>> so they are both correct and very explicit with the corresponding links, so >>> I’m not entirely sure which part is confusing. If you have a suggestions >>> that would clarify the confusion, please let me know and I’d be happy to >>> incorporate it. >>> >>> Cheers, >>> Simon >>> > -- Peter Dalgaard, Professor, Center for Statistics, Copenhagen Business School Solbjerg Plads 3, 2000 Frederiksberg, Denmark Phone: (+45)38153501 Office: A 4.23 Email: pd....@cbs.dk Priv: pda...@gmail.com _______________________________________________ R-SIG-Mac mailing list R-SIG-Mac@r-project.org https://stat.ethz.ch/mailman/listinfo/r-sig-mac
