![]() Having installed the package using the following command at the command line, I have /usr/include again, and my GCC 8.2.0 works once more. If they're careful, they could drive me away. ![]() I'm not dreadfully surprised to find Apple wanting to turn their backs on their Unix heritage, but I am disappointed. When all else fails, read the manual or, in this case, the release notes. In the Xcode 10.0 Release Notes, it says there is a package: /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkgĪnd you should install that package to have the /usr/include folder installed. If we are using Xcode 10, you will notice that if you navigate to the /usr in the Finder, you will not see a folder called 'include' any more, which is why the terminal complains of the absence of the header files which is contained inside the 'include' folder. But I can compile with /usr/bin/clang and /usr/bin/gcc - and the -v option suggests they're using InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin I then ran Xcode GUI (command-space, Xcode, return) and it said it needed to install some more software, but still no /usr/include. I ran xcode-select -install and it said " xcode-select: note: install requested for command line developer tools" and then ran a GUI installer which showed me a licence which I agreed to, and it downloaded and installed the command line tools - or so it claimed. A header ( _stdio.h, with leading underscore) was in my old /usr/include it is missing now (hence my problem with GCC 8.2.0). I've done a bit of comparison, and my Mojave machine has no /usr/include at all, yet /usr/bin/clang is able to compile OK. However, both the system /usr/bin/gcc and system /usr/bin/clang are working for me ( Apple LLVM version 10.0.0 (clang-1000.11.45.2) Target: x86_64-apple-darwin18.0.0 for both.) I have a problem with my home-built GCC 8.2.0 not finding headers in /usr/include, which is parallel to your problem with /usr/local/bin/gcc not finding headers either. I too have updated to macOS 10.14 Mojave and Xcode 10.0. I observe that if your GCC is installed in /usr/local/bin, you probably aren't using the GCC from Xcode that's normally installed in /usr/bin. I did that after installing Xcode 10.0, but a week or more ago, long before upgrading to Mojave. Have you tried running the main Xcode GUI interface? It may install some extra software for you and clean up. Very often, xcode-select -install has been the correct solution, but it does not seem to help this time. Make sure you have downloaded the latest 'Command Line Tools' package and run this from a terminal (command line): open /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkgįor some information on Catalina, see Can't compile a C program on a Mac after upgrading to Catalina 10.15.Įxtracting a semi-coherent answer from rather extensive comments… Preamble
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |