[MacPorts] #48345: Building for 10.4u SDK on 10.6 uses gcc-4.0 even though building directly on 10.4 uses the newer apple-gcc-4.2
#48345: Building for 10.4u SDK on 10.6 uses gcc-4.0 even though building directly on 10.4 uses the newer apple-gcc-4.2 --------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Keywords: | Port: --------------------------+-------------------------------- Ever since MacPorts 2.3.0, the default compiler on Mac OS X 10.4 is the MacPorts-provided version of the Apple GCC 4.2 compiler, because the latest Apple GCC provided by Tiger's Xcode is 4.0, which was deemed too old. However, if building on Snow Leopard using the Mac OS X 10.4u SDK, MacPorts uses Apple GCC 4.0 from Xcode. browser:trunk/base/src/port1.0/portconfigure.tcl@138099:488-492#L473 Why does it do this? This means that software built on Tiger uses a newer compiler than software built for Tiger on Snow Leopard. Shouldn't it use Apple GCC 4.2 from Xcode, or from MacPorts, to match what would happen when building directly on Tiger? I assume this is simply a remnant of when MacPorts < 2.3 used Apple GCC 4.0 on Tiger. Jeremy, you made this change in r92159 but no ticket number was referenced in the commit message. I remember Snow Leopard issuing an error saying the 10.4u SDK is not compatible with gcc 4.2, but that can't be true or else it wouldn't work directly on Tiger either, but it does work there. -- Ticket URL: <https://trac.macports.org/ticket/48345> MacPorts <https://www.macports.org/> Ports system for OS X
#48345: Building for 10.4u SDK on 10.6 uses gcc-4.0 even though building directly on 10.4 uses the newer apple-gcc-4.2 ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.99 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by jeremyhu@…): Wow, that was 3 years ago. Sorry, but the reasoning has left my brain at this point. I remember making that change and being upset that it was that way, but I don't recall exactly what the fallout was. Probably the easiest way to find out is to revert it and see what breaks. Since you're interested in that case, can you give it a whirl and see what falls out? It might be the case that gcc-4.2 doesn't work for some reason, but maybe I fixed that in apple-gcc-4.2. -- Ticket URL: <https://trac.macports.org/ticket/48345#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts