------- Comment #11 from carlos at codesourcery dot com 2006-08-22 21:02
-------
Created an attachment (id=12115)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12115&action=view)
When relocated do not add paths that contain the configured prefix.
Thanks for adding me to the CC.
A relocated compiler should never search the configured prefix for programs,
libraries or start files. A relocated compiler searching for files in the
configured prefix is troublesome. The configured prefix may contain a
conflicting toolchain, or a slow network path.
The old behaviour of searching the conifgured prefix is not what users expect
from a relocated toolchain.
Consider 3 types of paths:
1. Relocated paths.
2. Configured prefix paths.
3. Well known system paths.
The type 1 and type 3 paths are always added to our search lists. The type 2
paths are only added if the compiler is installed at the configured prefix.
This patch groups the 3 path types logically in gcc/gcc.c, and adds the paths
based on the wether the compiler is relocated or unrelocated.
Could you test this patch out and tell me if it helps?
There is a caveat, running 'make -k check' from the object directory may not
work. In certain cases, bare-metal targets for example, contains the required
start files to build and run the tests. I have an additional patch for this,
but it is still in testing.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17621
