------- Comment #46 from mmitchel at gcc dot gnu dot org 2009-02-02 22:00 ------- As I understand it, the complaint here is that GCC_EXEC_PREFIX being set affects HOSTCC, when HOSTCC is itself some other GCC.
But, we have to make sure that the newly built compiler searches the right directory. That's why GCC_EXEC_PREFIX is set. (You can fix this by arranging to fix GCC's build process, so that components are installed within the build tree in the same way they would be at install time, and then you can forget all about GCC_EXEC_PREFIX, -B options, and everything else. But, it's a huge project.) HOSTCC is an arbitrary compiler. It need not even be a GNU compiler. DejaGNU, "make check", etc. set all manner of random environment variables. Therefore, if you want to be robust, HOSTCC needs to set/unset any environment variables relevant to its operation. -- Mark -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36443
