On 5/12/23 2:01 AM, Po Lu wrote: > Jason Merrill <ja...@redhat.com> writes: > >> You shouldn't have to change any of those, just configure with CC="gcc >> -fwhatever". > > If it were so simple... > > Many Makefiles come with a habit of using not CC_FOR_BUILD, but just > `cc', to build programs which are run on the build machine. > > These programs are intended to be as portable as possible (naturally, > since Autoconf does not configure for the build machine). As a result, > they are typically written in the subset of ANSI C that will compile > with almost any C compiler, which is exactly what will cause problems > with GCC's proposed new defaults.
This sounds like a "you" problem. If your Makefiles are totally incapable of respecting the user's choice of C compiler, you may need to do the same thing that you'd do to compile it with any alternative compiler: add a directory to your path containing a wrapper script called "cc" which runs /opt/tinyc/bin/tcc "$@" or aarch64-linux-gnu-gcc "$@" or whatever. Although in this case it could just call /usr/bin/gcc -fpermissive "$@" -- Eli Schwartz
