https://bugs.kde.org/show_bug.cgi?id=295084
--- Comment #10 from Austin English <austinengl...@gmail.com> --- (In reply to Rhys Kidd from comment #9) > I'm almost certain there's a problem with your local copy of Xcode or with > multiple versions of Xcode tripping up. > > It's well documented that /usr/include is not present by default on recent > macOS, but is created via: > > $ xcode-select --install > > See further, as examples: > [0] > https://superuser.com/questions/995360/missing-usr-include-in-os-x-el-capitan > [1] https://discussions.apple.com/thread/7124628?start=0&tstart=0 Which is my point. If it's not present by default, it shouldn't be used. It's not included by default because there can be multiple versions of the SDK installed. Using the tip from https://stackoverflow.com/questions/6715454/what-is-the-default-path-for-osx-system-include-files-when-building-a-c-applic: $ echo "" | gcc -xc - -v -E On linux: ignoring nonexistent directory "/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/../../../../x86_64-pc-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/include /usr/local/include /usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/include-fixed /usr/include End of search list. on mac: #include "..." search starts here: #include <...> search starts here: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/8.0.0/include /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/System/Library/Frameworks (framework directory) End of search list. and indeed, I have a copy of mach_vm.defs in: /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/mach I have run xcode-select --install in the past (which is why I have git and other tools available, which work without /usr/include). I suspect the link was severed during an OS or SDK upgrade, but that's only speculating. If I re-run xcode-select --install, /usr/include exists and valgrind does compile. I still think it's a hack though, as this likely will break if someone tries to compile against a non-default SDK. Not to mention that it will presumably break in a future update, again. -- You are receiving this mail because: You are watching all bug changes.
