From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25215 invoked by alias); 12 Mar 2011 00:06:58 -0000 Received: (qmail 25205 invoked by uid 22791); 12 Mar 2011 00:06:57 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (74.125.121.67) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 12 Mar 2011 00:06:20 +0000 Received: from wpaz33.hot.corp.google.com (wpaz33.hot.corp.google.com [172.24.198.97]) by smtp-out.google.com with ESMTP id p2C06GJ7028937 for ; Fri, 11 Mar 2011 16:06:17 -0800 Received: from pzk12 (pzk12.prod.google.com [10.243.19.140]) by wpaz33.hot.corp.google.com with ESMTP id p2C06EIp027883 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Fri, 11 Mar 2011 16:06:15 -0800 Received: by pzk12 with SMTP id 12so540015pzk.11 for ; Fri, 11 Mar 2011 16:06:14 -0800 (PST) Received: by 10.142.117.21 with SMTP id p21mr8055799wfc.286.1299888374309; Fri, 11 Mar 2011 16:06:14 -0800 (PST) Received: from coign.google.com (dhcp-172-22-123-197.mtv.corp.google.com [172.22.123.197]) by mx.google.com with ESMTPS id w32sm6024263wfh.7.2011.03.11.16.06.13 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 11 Mar 2011 16:06:13 -0800 (PST) From: Ian Lance Taylor To: Michael Zintakis Cc: gcc-help@gcc.gnu.org Subject: Re: building native cross compiler References: <4D7A37DD.8030205@googlemail.com> <4D7A5420.4000608@googlemail.com> <4D7A8A4D.2080706@googlemail.com> <4D7AB3BB.7060208@googlemail.com> Date: Sat, 12 Mar 2011 00:06:00 -0000 In-Reply-To: <4D7AB3BB.7060208@googlemail.com> (Michael Zintakis's message of "Fri, 11 Mar 2011 23:43:55 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2011-03/txt/msg00125.txt.bz2 Michael Zintakis writes: > OK, speculating a bit and expanding this further with two more queries > - > if I do not know the target system in advance (i.e. the target for > GCC2) but this target is specified when the whole build process is > initiated, would the procedure we discussed on this thread differ? > > In other words, if, via a command line parameter or some environment > variable, the target system is specified when the build up process is > initiated and is, say, m68, and if I follow the process as discussed > on this thread, i.e.:- 1) build GCC1 (native-3stage-x86_64), then 2) > build x86_64-x-m68 (GCC2), then 3) build m68-native (GCC3), 4) use > GCC2 to compile the rest of the software for native m68 environment > and 5) prepare the image file for installation. Would that be the > right path to follow (i.e. same process but for different target > system)? Yes. > And my second (speculative) query - would it be wise to skip the first > step in this process (building GCC1) and build GCC2 instead and > continue the path from there? What would be the implications if such > path is to be followed (if at all possible that is)? It would be neither wise nor unwise. It would save some time, and there would be a very small risk that the compiler you used instead of GCC1 had a bug. (That has actually happened to me--a bug in the first compiler which subtly miscompiled the second compiler and caused problems in the code it generated--but not for many years.) Ian