#40888: tuntaposx @20111101 fails to build on Mavericks ------------------------+-------------------------------- Reporter: john@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: tuntaposx | ------------------------+-------------------------------- Comment (by john@…): Sorry, my mistake: this is working fine. Unfortunately, I don't seem able to close the issue for myself. -- Ticket URL: <https://trac.macports.org/ticket/40888#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#40888: tuntaposx @20111101 fails to build on Mavericks ------------------------+-------------------------------- Reporter: john@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: invalid | Keywords: mavericks Port: tuntaposx | ------------------------+-------------------------------- Comment (by t21@…): Replying to [comment:1 john@…]:

Sorry, my mistake: this is working fine. Unfortunately, I don't seem able to close the issue for myself.

Can you explain what you did to fix this? I see exactly the same error here. -- Ticket URL: <https://trac.macports.org/ticket/40888#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X

#40888: tuntaposx @20111101 fails to build on Mavericks ------------------------+-------------------------------- Reporter: john@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: invalid | Keywords: mavericks Port: tuntaposx | ------------------------+-------------------------------- Comment (by t21@…): Thanks John, I suspected that might be it. I've attached a patch to the Portfile, plus a patch for tuntaposx's Makefiles that removes the need for xcode-select --install. This is the only port I've come across which requires command-line tools to be installed on Mavericks; I suggest this fix (determining the SDK path at build time) is better than requiring the extra installation step of xcode-select --install. -- Ticket URL: <https://trac.macports.org/ticket/40888#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X

#40888: tuntaposx @20111101 fails to build on Mavericks ------------------------+-------------------------------- Reporter: john@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: invalid | Keywords: mavericks Port: tuntaposx | ------------------------+-------------------------------- Comment (by t21@…): Indeed it has. But with Mavericks/Xcode5, the shims that are installed by default mean that there's very rarely the need to install anything else. The only reason this port didn't build is because the source hard-coded the path /System/Library/Frameworks/Kernel.framework/Headers into the Makefiles. As John pointed out, those files exist even without installing the cmdline tools -- under the relevant SDK directory. I think this is a wider issue for MacPorts architecture: how many ports now fail if you don't install the cmdline tools? Of the 172 I installed on Mavericks, tuntaposx is the only one. I suggest it's worth considering whether dropping the requirement for xcode-select --install is possible at this stage. -- Ticket URL: <https://trac.macports.org/ticket/40888#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X

#40888: tuntaposx @20111101 fails to build on Mavericks ------------------------+-------------------------------- Reporter: john@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: invalid | Keywords: mavericks Port: tuntaposx | ------------------------+-------------------------------- Comment (by t21@…): OK, see you there. -- Ticket URL: <https://trac.macports.org/ticket/40888#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X