Opened 27 hours ago

Last modified 11 hours ago

#70799 new defect

R: all compilers blacklisted on macOS 15

Reported by: i0ntempest Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: sequoia Cc: barracuda156, kjellpk (Kjell Konis), cjones051073 (Chris Jones)
Port: R

Description

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?

Attachments (2)

main.log (286.4 KB) - added by i0ntempest 27 hours ago.
config.log (171.7 KB) - added by i0ntempest 27 hours ago.

Download all attachments as: .zip

Change History (8)

Changed 27 hours ago by i0ntempest

Attachment: main.log added

Changed 27 hours ago by i0ntempest

Attachment: config.log added

comment:1 Changed 20 hours ago by 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.

comment:2 Changed 20 hours ago by cjones051073 (Chris Jones)

Cc: cjones051073 added

comment:3 Changed 12 hours ago by 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.

comment:4 Changed 12 hours ago by 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.

Version 0, edited 12 hours ago by barracuda156 (next)

comment:5 Changed 11 hours ago by 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?

comment:6 in reply to:  5 Changed 11 hours ago by 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.

  1. 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: https://github.com/macports/macports-ports/commit/622eca8499b7d482142030eb8d61c0ff01a011c8

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

Note: See TracTickets for help on using tickets.