Time to check another compilation with GCC option -v added (in the makefile I used, setting UFLAGS adds the option to C compiler command line): $ make UFLAGS=-v CC=/usr/bin/gcc ww So, the probability is (AFAICS, after only an hour or two's effort) that Apple no longer support /usr/include - though it does still have a fully-loaded /usr/lib (no /lib though). There's no information in there that relates to this. Next step - find and read the release notes: Neither the System nor the Library directory contain anything very promising. $ ls /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/Įist SDKSettings.json System MacOSX.sdk MacOSX10.14.sdk MacOSX10.15.sdk $ ls /Library/Developer/CommandLineTools/SDKs There is a directory under /Library now: $ ls /Library/Developer usr/bin/gcc -I/Users/jleffler/inc -g -O3 -std=c11 -pedantic -Wall -Wextra -Werror -Wshadow -Wmissing-prototypes -Wpointer-arith -Wold-style-definition -Wcast-qual -Wstrict-prototypes -DHAVE_MEMMEM -DHAVE_STRNDUP -DHAVE_STRNLEN -DHAVE_GETDELIM -o al al.c -L/Users/jleffler/lib/64 -ljl Using /usr/bin/gcc, it is now possible to compile programs: $ make CC=/usr/bin/gcc al InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin $ /usr/bin/gcc -versionĬonfigured with: -prefix=/Applications/Xcode.app/Contents/Developer/usr -with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/atform/Developer/SDKs/MacOSX.sdk/usr/include/c++/4.2.1Īpple clang version 11.0.0 (clang-1100.0.33.8) That's a useful step (though I didn't definitively check whether they were present before). When doing so, it claimed that it downloaded the command line utilities, and it ensured that /usr/bin/gcc and /usr/bin/clang etc were present. One of the other bits of advice in the previous question was to run: xcode-select -install However, that did not reinstate /usr/include or the directory under /Library.
CODELITE FOR MAC MOJAVE INSTALL
It wanted to install some extra components, so I let it do so. Immediately after the upgrade, I ran XCode 11.0. If you build your own GCC or other compiler, you will (probably) need to configure it to find the system libraries under the Xcode application directory. Both /usr/bin/gcc and /usr/bin/clang will find the system libraries four directory levels below: /Applications/Xcode.app/Contents/Developer/Platforms/… Using the Apple-provided GCC (actually, that's Clang by any other name, as the version information shows) or Clang avoids problems. It appears that Apple considers /usr/include as something that has gone the way of the dodo - it is extinct - or maybe it's like Monty Python's Parrot. Ln: /usr/local/include//tkPlatDecls.h: File exists Ln: /usr/local/include//tkDecls.h: File exists Ln: /usr/local/include//tk.h: File exists Ln: /usr/local/include//tclTomMathDecls.h: File exists Ln: /usr/local/include//tclTomMath.h: File exists Ln: /usr/local/include//tclPlatDecls.h: File exists
Ln: /usr/local/include//tclDecls.h: File exists Some of the headers already exists, like this: ln: /usr/local/include//tcl.h: File exists It worked for me! the following command line will take care of all the problems: sudo ln -s /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/* /usr/local/include/ We just need to create symlink for all the headers file into this folder: /usr/local/include/ xcode-select -installĪctually, you can do it! Actually all the C headers are found here in this folder: /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/ Before you proceed, make sure to install xcode command line tools.
0 kommentar(er)
