R: all compilers blacklisted on macOS 15

[i0ntempest]

Building R on macOS 15 now gives: All compilers are either blacklisted or unavailable, and then fails. Time to switch to new clang and gcc?

[cjones051073 (Chris Jones)]

Correct, currently only gcc14 and clang 18 or 19 work on macOS 15. This *may* improve in the future, but also quite possibly will remain a restriction. So now would indeed be a good time to bump the versions R forces.

[markemer (Mark Anderson)]

Has 67144 been fixed by R upstream? Seems like 17+ was causing problems. But yeah both gcc13 and clang < 18 are broken on macOS 15 now, so that's not great.

[barracuda156]

Release of a broken OS was not something we were prepared for :)

Changing compilers for R will be a pain. That’s a lot of stuff to rebuild. I have no idea whether clang-18 gonna work. gcc14 is probably safe.

UPD. Well, “is safe” may be an overstatement, since both gcc14 and clang18+ changed many warnings to errors, so that is likely to break an unknown number of ports. However since all systems on buildbots use clang for C/C++, only myself gonna see breakages with gcc14. gfortran14 should be safe – I can’t remember anything being broken by it.

[i0ntempest]

I thought compiler path is no longer baked in and we no longer follow the upstream guideline that says R base and packages should be built using the same compiler?

If this is the case how much stuff do we need to rebuild?

[barracuda156]

Replying to i0ntempest:

I thought compiler path is no longer baked in and we no longer follow the upstream guideline that says R base and packages should be built using the same compiler?

As of now it is, AFAIK. Unless someone changed that without me noticing.

If this is the case how much stuff do we need to rebuild?

I recall rebuilding was pretty unpopular last time and I rather avoid another week-long discussion, so let others decide. I can always fix this for myself at least.

16. S. As a matter of fact, a number of ports have been broken earlier by skipping revbump when it was due. So I had to add these hacks whenever CI shown an error: [622eca8499b7d482142030eb8d61c0ff01a011c8/macports-ports]

Those are not numerous, given total number of R ports, but there may be more.

[cjones051073 (Chris Jones)]

Replying to barracuda156:

Release of a broken OS was not something we were prepared for :)

Changing compilers for R will be a pain. That’s a lot of stuff to rebuild. I have no idea whether clang-18 gonna work. gcc14 is probably safe.

UPD. Well, “is safe” may be an overstatement, since both gcc14 and clang18+ changed many warnings to errors, so that is likely to break an unknown number of ports. However since all systems on buildbots use clang for C/C++, only myself gonna see breakages with gcc14. gfortran14 should be safe – I can’t remember anything being broken by it.

The OS is not (completely) broken, just has dropped for now support for old compilers. This is natural progression and something you should be prepared for.

[cjones051073 (Chris Jones)]

b.t.w. you don' have to, for now, change the compilers used on macOS14 or older. In the longer term it would be a good idea, but you could just bump the version for macOS15+ to versions now supported there, but on macOS14 or older keep things as they are. Given nothing builds on macOS15 at present you would not even need to rev bump anything.

[markemer (Mark Anderson)]

Replying to cjones051073:

b.t.w. you don' have to, for now, change the compilers used on macOS14 or older. In the longer term it would be a good idea, but you could just bump the version for macOS15+ to versions now supported there, but on macOS14 or older keep things as they are. Given nothing builds on macOS15 at present you would not even need to rev bump anything.

Yep - that might be the best move - that way we can see how well it works and build with the new stuff later on everything. We can't break macOS 15 R builds more than they already are.

[cjones051073 (Chris Jones)]

As it can hardly make things worse for R users on macOS15+

​https://github.com/macports/macports-ports/commit/4112440c528a827019b8a1b38adabd0d21aded3e

Not an R user myself, but seems fine at building R and a few test R-XYZ ports.

[markemer (Mark Anderson)]

Clang 17 and 16 are working now (and 14 and 15 are on the way!) so we might want to revert 411244 and close the ticket. Although we should probably open a new one to bring R to at least clang 17 if not 18/19 when possible.

[markemer (Mark Anderson)]

Replying to markemer:

Clang 17 and 16 are working now (and 14 and 15 are on the way!) so we might want to revert 411244 and close the ticket. Although we should probably open a new one to bring R to at least clang 17 if not 18/19 when possible.

After talking to barracuda156, gcc13 is needed for gfortran, so we're still kinda stuck on macOS 15.

[cjones051073 (Chris Jones)]

Now macOs15+ are on clang-18 and gcc-14 I would not roll them back.