#61480 closed defect (fixed)
duti @1.5.4: fatal error: 'CoreFoundation/CoreFoundation.h' file not found
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | newtonne |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.6.4 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
Port: | duti |
Description
duti fails to build, for example on 10.10:
clang: warning: no such sysroot directory: '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk'
./util.c:1:10: fatal error: 'CoreFoundation/CoreFoundation.h' file not found #include <CoreFoundation/CoreFoundation.h> ^
It is wrong for the build to try to determine what SDK to use. MacPorts will tell the build what SDK, if any, should be used; the build should not second-guess that.
The problem here happens because on 10.10 we are using Xcode 7.2.1 which does not contain the 10.10 SDK and only contains the 10.11 SDK. For years Apple has been introducing new versions of Xcode that contain only the latest OS SDK, even if that version of Xcode runs on the previous version of the OS.
Change History (3)
comment:1 Changed 4 years ago by DanielSmedegaardBuus (Daniel Smedegaard Buus)
comment:2 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:3 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign added |
---|
Note: See
TracTickets for help on using
tickets.
Hello :)
I'm completely new to Macports — only been here a few hours — so I have no idea how this is all supposed to go down, but I too am on 10.10, and ran into this error.
I got duti installed by manually editing duti's
Portfile
to point to the correct SDK:configure.args-append --with-macosx-sdk=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk
And then doing
sudo port install
from themacports-ports/sysutils/duti
directory.Thing is, this is clearly not the correct way to do this, but again I know very little about Macports at this point. AFAICT, @newtonne is the maintainer for this port? Or is it not being maintained any longer? It seems like this is a simple fix to make, but I don't know how, if, or who to poke :D
Cheers :)