PCH and moving gcc binaries after installation

[Dan Kegel]

Moving an installed gcc/glibc crosstoolchain
to a different directory was not allowed
for gcc-2.96 and below, I seem to recall,
but became permissible around gcc-3.0.
(Sure, there are still embedded paths,
but they don't seem to be used in practice.
I don't really trust it, but that's what I observed.)
That sound right?

OK, so what's the story with PCH?  Does it break
the above assumption?  I just looked through
a gcc-3.4.2 install, and found something that looks
like PCH files with embedded paths in e.g.
/opt/crosstool/i686-unknown-linux-gnu/gcc-3.4.2-glibc-2.3.3/include/c++/3.4.2/i686-unknown-linux-gnu/bits/stdc++.h.gch/O2g

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?
- Dan

-- 
Trying to get a job as a c++ developer?  See http://kegel.com/academy/getting-hired.html