I can never remember this so, to stop me having to constantly refer to my non-work computer, here is how to accept the new Xcode update:
sudo xcodebuild -licence acceptYou Shut Down Your Computer Because of a Problem
- I didn’t
- If I did tell me what the problem was.
- If you’re not going to tell me what the problem was shut the hell up because how am I supposed to fix it if I don’t know what the problem was?
The easy fix is to just remove everything in: /Library/Logs/DiagnosticReports/
I mean, it’s not like I’m going to look at it, anyway.
Ref: https://iboysoft.com/howto/you-shut-down-your-computer-because-of-a-problem.html
Pet Hates
So, for no real reason, I dislike using package managers on my Mac. I don’t know why, I just do. I’m fine with them on Debian or whatever but not on my Mac. That makes it really interesting when I get a new machine and have to compile everything from scratch. Just getting cURL running with SSL and SSH support ends up looking something like this:
cURL: depends on OpenSSL, libSSH2
libSSH2: depends on zlib, OpenSSH, CMake
CMake: depends on CMocka
CMocka: depends on DOxygen, graphviz
DOxygen: depends on flex, bison, libiconv, make
Still, once it’s all built and done I have a nice, shiny, new cURL command.