Greetings, All. I wish to build gcc-9.2.0 on my M1 Mini. Note that I am not really interested in gcc, as Apple's clang compiler is fantastic, but actually in gm2, which is written as a front end to gcc. Now, I understand that the gcc folk do not support M1, so I tried to build a cross-compiler to run under Rosetta-2, namely set both host and build to x86_64-darwin. The build trundles along (well, it flies -- this h/w is fast!) until it reaches "fixing" the header files. The path /usr/include is hard-coded throughout the build tools and it comes to a screeching halt. So how to fool the gcc build tools? The system will not let me create a symlink in /usr. I tried prepending an appropriate path from xcrun to the hard-code path but there are a *lot* of them. This is not a priority so I can just await M1 support. Thank you. jog

Greetings, All. Running on M1 Mini with case-sensitive file system, /usr/bin/CC pop up a little window telling me to install the CLI utilities. I did so (and About tells me that they are installed along with Xcode 12.4). But invoking /usr/bin/CC pops up the same window again. Please help.