Skip to content

R does not build out of the box on Ventura

4 messages · Peter Dalgaard, Brian Ripley

#
The problem being that devQuartz.c uses a deprecated and now removed 
interface (ATS).

Building with --without-aqua will work.

I am sure that Simon will fix this, but not in time for 4.2.2 which is 
in code freeze.

Note this only affects building: as the CRAN binary distributions are 
built on much older versions of macOS they should continue to build. 
This is purely a heads up for those building from source that they may 
want to delay upgrading to Ventura (but someone needed to to find the 
issue).

For the first time for quite a while, upgrading to Ventura removes the 
Command Line Tools which need reinstalling.
#
Thanks for the heads-up, Brian.

Older binaries still install and run on Ventura, I hope?

I intend to hold off updating at least the office machine (which builds the tarballs) until 4.3.0, for platform stability. The push for Ventura doesn't seem to have arrived here yet, but probably will come in a few days.

By the way, I have been getting update requests for "Command Line Tools beta n for Xcode 14.1", even though I have no recollection of signing up for beta versions. I'm rather reluctant to install those. 

- Peter

  
    
#
On 25/10/2022 10:53, peter dalgaard wrote:
They do, in so far as I have tested (which included some plotting).
That's an Apple trait. As you are on macOS 12.x, I would feel free to 
ignore them: even those for the released CLT 14 (although (I was using 
that on 12.6 for a month with no issues).

  
    
1 day later
#
On 25/10/2022 10:13, Prof Brian Ripley wrote:
Having found the relevant release note:

https://developer.apple.com/documentation/macos-release-notes/macos-13-release-notes

I can add a bit more info.

1) The build failure is only seen if you are using the macOS 13 SDK.  It 
has been possible to build with the 12.3 SDK.  But if you don't yet have 
the macOS 13 SDK you are likely to get upgraded to it soon.  Look at

ls -l `xcrun -show-sdk-path`

to see what you have (it is a symlink, to MacOSX13.0.sdk on my system).

2) If you are, a workaround is to add something like

-mmacosx-version-min=12.0

to CFLAGS.