Re: PCH and moving gcc binaries after installation

[Marcin Dalecki <martin at dalecki dot de>]

On 2005-03-30, at 08:37, Dan Kegel wrote:
> Since I need to handle old versions of gcc, I'm
> going to code up a little program to fix all
> the embedded paths anyway, but I was surprised
> by the paths in the pch file.  Guess I shouldn't
> have been, but now I'm a little less confident
> that this will work.  Has anyone else tried it?

I did try it some time ago. Well the fallout was that it's all really
painful. There seem to be all different path handling code in
gcc.c
collect
cpp
and cc1

Then you have to take in to account that the path handling will be
subtly different whatever configure did feel like cross compiling or 
not.
There seem to be some special VMX (shrug) trickery sparcled around.
One can see that the collect code does contains some independent not 
finished
attempt to unify all of the above. Frequently enough spec files will 
come from
behind and bite you.

Look for example at the requirement to double install as and 
i386-linux-as
and to have the as first in PATH in a cross build environment. It's just
accidental.

So the short story is: Yes it's a "huge" mess.

The solution involved basically just patching all of the above listed 
tools
to include and additional mechanism first before even starting to muddle
through the defaults.