On 6 Jun 2019, at 11:19 , Prof Brian Ripley <ripley at stats.ox.ac.uk> wrote:
On 06/06/2019 09:31, peter dalgaard wrote:
FWIW, no updates are suggested for the source-building machine in my office, also running Mojave. (June 5 was Constitution Day and Election Day, so I have been away from the machine until now.)
It stopping nagging me yesterday afternoon, so likely it was an Apple snafu. (I heard from others who had been caught by this, and of course Apple allows for 'automatic' updating so this could happen in the background.)
We do need to keep an eye on the tools though. My current setup is an -um- eclectic mix (*) of old and new tools, some of which are 32 bit, and this is going to be a problem in 10.15 Catalina. I did try getting the tools better in line with Simon's setup at some point, but there were hiccups and then I ran out of time and couldn't risk collateral damage.
You have a few months yet. The residual 32-bit applications I have are from Adobe, e.g. old uninstallers.
On 4 Jun 2019, at 17:10 , Prof Brian Ripley <ripley at stats.ox.ac.uk> wrote:
My Mojave machine today prompted me to update to version 11 of Command Line Tools (apparently 'beta 1', but I am not a Beta tester).
In short: don't do that (you can revert to 10.2.1 from the URL above, at least if your Apple ID has (free) developer privileges).
CoreFoundation.framework has been removed (and its headers are used in a couple of spots compiling R).
Further its seems that /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg is no longer included and setting CPPFLAGS did not suffice.
Hopefully we will have solutions in due course, but that version is really for 10.15 Catalina which is months away ('in the Fall', whenever that is).
--
Brian D. Ripley, ripley at stats.ox.ac.uk
Emeritus Professor of Applied Statistics, University of Oxford