#41056: Mavericks + gcc48 build breaks + fixes ----------------------+-------------------------------- Reporter: david@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: invalid | Keywords: mavericks Port: gcc48 | ----------------------+-------------------------------- Changes (by cal@…): * keywords: => mavericks * status: new => closed * resolution: => invalid Comment: Replying to [ticket:41056 david@…]:
1) After Mavericks upgrade /usr/include is gone
*) FIX: ln -sf $(xcrun --show-sdk-path)/usr/include /usr/include
`/usr/include` isn't gone, it's part of the command line tools. Revert the symlink and install the command line tools using `xcode-select --install`. This will also automatically fix MacPorts' `./configure` script which will fail to find Tcl without the command line tools.
2) couldn't open "/System/Library/Frameworks/Tcl.framework/Versions/8.5/Resources/tclIndex": no such file or directory
This is a red herring. MacPorts does not need this file, yet somehow this error message shows up sometimes.
*) FIX: make Macports TCL (which is currently 8.6.1) a dependency + arrange for Macports TCL to be used instead of system TCL
That is currently not possible, because MacPorts base is not compatible with Tcl 8.6 (due to MacPorts overriding the `try` statement new to 8.6). Also using MacPorts Tcl to build MacPorts would create a very simple way for users to shoot themselves, which is why we're not doing that, at least not without adding additional safeguards.
It appears TCL is no longer provided as a Framework in OSX. There is no Tcl.framework directory or tclIndex file on the disk anymore.
Tcl is still available on OS X, but you have to install the Command Line Tools in order to build against it. Installing the Command Line Tools will also fix the problem you see with the GCC build. -- Ticket URL: <https://trac.macports.org/ticket/41056#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X