------- Comment #51 from janis at gcc dot gnu dot org 2009-02-06 19:30 ------- Mark pointed out way back in comment #9 that GCC used to effectively do the same thing by searching the install directory even without GCC_EXEC_PREFIX. I understand that setting it makes people nervous, but I haven't seen any specific evidence that setting it is actually a problem. I often reuse an existing install directory, and if there were problems with picking up GCC components from GCC_EXEC_PREFIX during testing then I would have seen failures from new tests.
Rob, you haven't convinced me that there is a problem. I'd want to see specifics, like building a particular revision and then running a particular test using make -k RUNTESTFLAGS="... xx.exp=testname.c" check I posted a patch last week that cleans things up a bit by setting GCC_EXEC_PREFIX in one place and switching it back again for running $HOSTCC; see http://gcc.gnu.org/ml/gcc-patches/2009-01/msg01496.html . -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36443
