From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!news2.kpn.net!news.kpn.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader3.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: self-hosting gc References: <87elj5i2rf.fsf@becket.becket.net> <87zo1nvca6.fsf@becket.becket.net> <87eliy203l.fsf@becket.becket.net> <3224355185019060@naggum.net> <87henu2o3a.fsf@becket.becket.net> <3224397443760956@naggum.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3224431235976594@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 19 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 06 Mar 2002 19:20:27 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader3.kpnqwest.net 1015442427 193.71.199.50 (Wed, 06 Mar 2002 20:20:27 MET) NNTP-Posting-Date: Wed, 06 Mar 2002 20:20:27 MET Xref: archiver1.google.com comp.lang.lisp:27968 * 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.