C 代码在 MacOS Catalina 或 Big Sur 中无法编译

Question

I am unable to compile C code on neither MacOS Catalina nor Big Sur. I see the header files present in /usr/include/ , but I get errors from my C compiler.

Current error messages I get from the compiler are:

• For "#include <time.h>" => error: cannot open source file "time.h"
• For "#include <stdint.h>" => error: cannot open source file "stdint.h"

What I've tried:

• I tried sudo installer -pkg /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg -target / and it says "upgrade successful", but does not resolve any errors.
• I tried uninstalling and reinstalling XCode (Version 10.1)
• I tried downloading the.pkg file you mentioned (because I was missing it) but was told my macOS version was too new
• The files I need are stored in /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include , so we added a new CPATH and PATH variable (separately) for that path to ~/.bash_profile and /etc/paths
• I tried to provide #include statements with explicit paths to those files, which quickly spiraled out of control
• I tried to move all of the required files from the above directory to my project folder and changing the paths appropriately in the code
• I tried to run sudo ln -s /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include
• The files should also be stored in Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include , so I tried doing the above steps with this path as well

Any advice would be helpful. Thank you!

To provide more clarity based on a comment from Joshua below, these are the steps I followed to set up the 32-bit ARM cross-compiler:

1. sudo installer -pkg /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg -target /

2.  brew install gmp brew install mpfr brew install libmpc

3. Downloaded "binutils-2.36.tar.xz" from here

4. Outside of the binutils directory, created a directory called "build32"

5.  ../binutils-2.36/configure --target=arm-none-eabi --disable-nls --enable-languages=c --without-headers make -j4 all sudo make install

6. Downloaded "gcc-arm-src-snapshot-10.2-2020.11.tar.xz" from here

7. Inside the main directory, created a subdirectory called "build32"

8.  ../gcc-arm-src-snapshot-10.2-2020.11/configure --target=arm-none-eabi --disable-nls --enable-languages=c --without-headers make -j4 all-gcc sudo make install-gcc

Answer 1

I ended up switching to a Windows Subsystem for Linux setup on another machine for what I was working on. Another option is to set up a VM on the Mac. I could not figure out another solution for getting it to "just work" on the Mac. Thanks to everyone for the suggestions!

For those looking to pivot to WSL, follow this setup guide.

For those looking to go the VM workaround route, this is one process that was graciously recommended to me:

"1. Install Virtualbox from https://www.virtualbox.org/

2. Install Vagrant from https://www.vagrantup.com/

3. Download the prebuilt ARM gcc cross compiler from the link above in my question.

4. Move the download file into the project directory and run the following command to extract it:

   tar -xvf gcc-arm-10.2-2020.11-x86_64-arm-none-eabi.tar.xz

5. Download this Vagrantfile (fyi 'this' triggers a download of said file) and move it to the project directory as well. This file tells vagrant how to setup the VM. It will mount the project directory as well as the SD card. On line 41 of this file it tells vagrant where the SD card is located so change the first path on this line to where your SD card is located. Additionally, because the project directory is mounted, you can still edit the project files locally on your machine instead of having to use what's on the VM if you use this solution.

6. After all that, you should be ready to create/start the VM using the command vagrant up. To log into the VM, vagrant ssh after the vagrant up command finishes. Your project files should be located in the /vagrant directory. You are now all setup to compile the project and if you run make cp it should compile the project and copy it over to the SD card.

7. To shutdown the VM you can run vagrant halt to shutdown the VM, and to get rid of the VM you can run vagrant destroy. vagrant destroy will not delete any of the files that were shared from your computer to the VM."