[MacPorts] #41783: Always use Mac OS X SDK
#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
#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 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by william@…): I believe that https://trac.macports.org/ticket/41589 may be related. It looks like a different value for deployment target between configure and build phases. Is it related, or am I mistaken? -- Ticket URL: <https://trac.macports.org/ticket/41783#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#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 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by ryandesign@…): Replying to [comment:3 william@…]:
I believe that #41589 may be related. It looks like a different value for deployment target between configure and build phases. Is it related, or am I mistaken?
Not related. -- Ticket URL: <https://trac.macports.org/ticket/41783#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#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 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by ryandesign@…): I've attached the patch I'm testing for this, but it needs to be updated for changes made in r115429, and it can be simplified if #41782 is resolved first. -- Ticket URL: <https://trac.macports.org/ticket/41783#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#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 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by ryandesign@…): Updated and simplified patch attached. -- Ticket URL: <https://trac.macports.org/ticket/41783#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
#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 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by ryandesign@…): The problem I'm encountering using this patch is when ports build using FSF GCC. Then I get e.g.: {{{ gcc-mp-4.8: error: unrecognized command line option '-syslibroot' }}} -- Ticket URL: <https://trac.macports.org/ticket/41783#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
#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 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by mojca@…): Jeremy's opinion is that specifying SDK shouldn't ever be needed at all. Which is exactly the contrary to what this patch is trying to do. Always specifying SDK will most certainly break `libc++` on 10.6 (but then again `libc++` could install files inside the SDK). As a consequence at the moment it would break '''everything''' on 10.6 if `libc++` is chosen by default in MacPorts configuration. My experience tells me that specifying SDK explicitly is often needed, in particular when compiling for an older Mac OS X version (I'm not excluding software bugs for the problems). See #44125 and please talk to Jeremy. -- Ticket URL: <https://trac.macports.org/ticket/41783#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts