Toolchain relocation

[Dave Murphy]

H. J. Lu wrote:
> It may be related to
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14435
>
> Can you try
>
> http://gcc.gnu.org/ml/gcc-patches/2006-01/msg01757.html
Tried that but no difference.

I had a look through gcc.c and noticed that standard_exec_prefix and 
standard_libexec_prefix are constants which refer to the configured 
install path. gcc_exec_prefix and gcc_libexec_prefix are the equivalent 
paths adjusted for the relocated toolchain but the unadjusted variables 
are used in several places. The attached patch switches them for the 
adjusted variables and is a partial fix for my problem but unfortunately 
isn't the whole story. The relocated compiler is still checking for 
includes in the configured location but all the directories reported 
from -print-search-dirs are now relocated.

Unfortunately I still don't quite understand how the include paths are 
determined so I haven't made much progress in tracking the problem 
there. Is there any reason why -print-search-dirs doesn't report include 
paths as well?

One caveat with this patch is that the make_relative_prefix calls are 
commented on VMS so this might utterly break the compiler on that platform.

Could someone check if this is the right approach and possibly point me 
in the right direction to adjust the include paths as well?

Dave
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gcc_exec_prefix.patch
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20060415/1d79ab56/attachment.ksh>