gcc is a front end for cc1 (cc1 is the actual C compiler). During compilation, gcc will call cc1 as needed. On my Linux box (SUSE 10), cc1 wasn't in the path. I had to go dig it up. On my box I found it under /usr/lib/gcc/some distro-specific stuff/cc1. You can probably use /usr/lib as a starting point and then do a recursive find for the file name.
I suggest you track down the cc1 that is being called, and when you are in that directory, type './cc1 --version'. My guess is that you may have upgraded gcc and somehow missed upgrading cc1, though how that might happen isn't clear to me. It may be that for some reason, gcc is looking in the old directory instead of the one with the new cc1.
I strongly recommend that you *not* edit out those lines in your Makefile, because they refer to security features that will help you avoid buffer overflow exploits. Without them, C programs will compile without these safeguards. This is a Bad Thing (tm).
In reply to Re: Should I get another gcc?
by spiritway
in thread Should I get another gcc?
by betacentauri
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |