Sorry Ian, I am not thinking straight! I just realised that gcc provides --with-build-sysroot for that particular purpose so I may as well utilise it and point it to my staging area.Right! Could this be changed *after* installing gcc (via the spec file perhaps)? If not, then I could think of another way which might do the trick - use the "correct" prefix (say /usr) and then when I do "make install" specify DESTDIR to point to my buildroot directory where I would keep all of the other programs and tools for my destination image. Would that work?Thanks Ian. So, in other words the prefix value is only used during installation and then "forgotten" about, right?It's not forgotten. It remains the default. But gcc will also try to find the associated libraries, header files, etc., based on the location of the gcc executable itself.
One other query with regards to this - cast your mind back to my GCC1, 2 and 3 scenario when I needed to build the last gcc - GCC3 - which was to be used to compile and run on the host system (ppc).
Am I likely to encounter some unexpected difficulties if I use my cross compiler - GCC2 (which works wonders by the way!) to compile and build GCC3? I know I have to run configure with --build=x86_64 --host=powerpc --target=powerpc but am not sure if this is going to work (I also have the powerpc essential libraries - mpc, ppl, mpc, mpfr, cloog, full glibc already compiled and installed for the target architecture in my staging area).
MZ
