On 16 January 2012 14:49, Hans Aberg wrote: > On 16 Jan 2012, at 15:31, Jonathan Wakely wrote: > >>> The config.log of this directory just indicates a program doing the check >>> that will fail (now overwritten by new ./configure && make). >> >> Do not run ./configure, see http://gcc.gnu.org/wiki/InstallingGCC and >> http://gcc.gnu.org/wiki/FAQ#configure and >> http://gcc.gnu.org/install/configure.html - you have to try pretty >> hard to avoid that tip if you read any installation docs at all. > > Too late! Actually, I ended up on > http://gcc.gnu.org/svn.html > which does not say anything about install. Perhaps add a note.
The installation docs are already linked from the front page. Anyone wanting to install GCC should probably read them. > It is a good idea to do it from outside the directory - 'make clean' does not > work. Yes, that's one of many reasons not to run ./configure. Building outside the source tree means you can just delete the entire build directory and start again.