> On Sep 21, 2016, at 12:15, Adam Dershowitz <de...@alum.mit.edu> wrote: > > That comment does not make it at all clear what those of us who updated to > Xcode 8 (but not beta!) but are still on OS X 10.11 are supposed to do.
If you don't need the CLTools, do nothing. If you need the CLTools, install the latest version (or likely just stick with the version that you have if you already have them). > I have posted a ticket about building cmake that seems to be because it is > trying to use 10.12 SDK, but it is not clear how to work around that. If a port is using an SDK and you haven't configure it to do so, that's a port bug. > Perhaps the answer is to downgrade to Xcode 7, and stay away from 8? (It is > a big download!) Why? Fix the bug in the port. > Or, it might be that just the 10.11 command line tools is enough? The 10.11 CLTools installs the 10.11 headers to /. Your issue with cmake is likely that the port is (incorrectly) trying to use the 10.12 SDK and expecting it to match the base system somehow... ? > > --Adam > > > >> On Sep 21, 2016, at 2:44 PM, Lawrence Velázquez <lar...@macports.org> wrote: >> >> Jack Howarth has noted on IRC that that Apple will not be releasing >> a Command Line Tools package for Xcode 8 on El Capitan [*]. >> >> There is no Command Line Tools (OS X 10.11) for Xcode >> 8 package. Xcode 8 contains SDKs that are incompatible >> with earlier toolchains. Developers who want to make use >> of the Xcode 8 SDKs from the command line must choose >> the SDK with xcode-select. Developers on OS X El Capitan >> who have installed versions of the Command Line Tools >> (OS X 10.11) for Xcode 8 Beta should install Command >> Line Tools (OS X 10.11) for Xcode 7.3.1. (28234439) >> >> Do we need to adjust our installation instructions to account for this? >> The consequences of mixing the Xcode 7 CLT with Xcode 8 are not clear to >> me; maybe it's not a problem at all. >> >> [*]: >> http://adcdownload.apple.com/Developer_Tools/Xcode_8.1_beta/Release_Notes_for_Xcode_8.1_beta.pdf >> >> vq >> _______________________________________________ >> macports-dev mailing list >> firstname.lastname@example.org >> https://lists.macosforge.org/mailman/listinfo/macports-dev >
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list email@example.com https://lists.macosforge.org/mailman/listinfo/macports-dev