http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53384
--- Comment #2 from John T <jrt at worldlinc dot net> 2012-05-17 16:47:08 UTC --- (In reply to comment #1) > Are you building in the source directory? No. I untarred all the source in /usr/local/gcc-4.6.3, all except the go tarball, and built in my home folder ~/bld463. I also did a diff between the configure for 4.6.1 and 4.6.3 and didn't find anything that appeared relevant, just changes in references to libiberty. The section that tests for value changes for v. 4.6.3 and wrongly flags the change in CC starts at configure line 2091, I think. Just below that section is the start of the main body of the script where some values including the compiler execution string are set. Since the configures for 4.6.1 and 4.6.3 are nearly the same and I just built 4.6.1 successfully last night, I don't have a clue as to what's messing up the handling of the compiler value. I don't know scripting.
