http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42955
Brooks Moses <brooks at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2010-04-22 20:17:36 |2013-07-26 20:17:36
CC| |brooks at gcc dot gnu.org
Severity|normal |critical
--- Comment #7 from Brooks Moses <brooks at gcc dot gnu.org> ---
I have reconfirmed this, in the following things, all for different targets:
* A downloaded Sourcery CodeBench Lite Edition 2010.09 (GCC 4.5.1 with patches)
* A downloaded Sourcery CodeBench Lite Edition 2013.05 (GCC 4.7.3 with patches)
* A local build of our google/gcc-4_8 branch.
* A build of current development trunk.
The problem is very straightforward:
The ${target}/bin/gcc is installed from "gcc-cross", which is created by a
simple "cp" command from "xgcc" -- see the "gcc-cross$(exeext):" rule in
gcc/Makefile. (The bin/${target}-gcc is installed from "xgcc".) Thus, the
decorated and undecorated gcc executables are identical.
And, if we run this executable under strace, we will find that it looks for cc1
in things under "../libexec", but not under "../../libexec", which would be the
correct path for the undecorated executable.
