#41783: Always use Mac OS X SDK --------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.2.99 Keywords: | Port: --------------------------+-------------------------------- MacPorts 2.2 currently only uses a Mac OS X SDK if the macosx_deployment_target is different from the current Mac OS X version, or on PowerPC on 10.4 when building universal. The only reason that I can see why we're not using an SDK in all cases is that on 10.4 using an SDK introduces problems linking with non-SDK libraries (such as MacPorts-provided libraries); see e.g. #25053. But changing Tiger's default compiler from gcc-4.0 to apple-gcc-4.2 may fix that problem; see #41782. Using an SDK in all cases (or at least on Mavericks and later) seems to fix a kde build failure on Mavericks with MacPorts trunk; see #41321. I've made a patch for this and will test it out for awhile on my various systems to see if this introduces any new problems. -- Ticket URL: <https://trac.macports.org/ticket/41783> MacPorts <http://www.macports.org/> Ports system for OS X