Subject: Re: self-hosting gc From: Erik Naggum <email@example.com> Date: Wed, 06 Mar 2002 19:20:27 GMT Newsgroups: comp.lang.lisp Message-ID: <firstname.lastname@example.org> * Tim Bradshaw | I assume they add support for the new target to gcc, compile gcc on an | existing system targeted at the new system and then run this new compiler | on the new system. This is probably doable, but in my experience with cross-compilation, you do not just generate code, you effectively generate a module that works with a much larger system. To make this _really_ work, you have to have intimate knowledge of the target system. Since the compiler is often the first thing you build on a new system in order to build the other tools you want to use there, my thinking is that you save a lot of time using a pre-existing compiler and like tool, particularly to ensure that you get the linking information right for that particular environment, what with all the shared library dependencies and whatnot. /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief.