From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12839 invoked by alias); 13 Mar 2011 22:10:37 -0000 Received: (qmail 12829 invoked by uid 22791); 13 Mar 2011 22:10:35 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST X-Spam-Check-By: sourceware.org Received: from mail-wy0-f175.google.com (HELO mail-wy0-f175.google.com) (74.125.82.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 13 Mar 2011 22:10:31 +0000 Received: by wyb40 with SMTP id 40so3941505wyb.20 for ; Sun, 13 Mar 2011 15:10:29 -0700 (PDT) Received: by 10.227.195.211 with SMTP id ed19mr4479662wbb.208.1300054229052; Sun, 13 Mar 2011 15:10:29 -0700 (PDT) Received: from [127.0.0.1] (xvm-174-176.ghst.net [95.142.174.176]) by mx.google.com with ESMTPS id x1sm5569223wbh.8.2011.03.13.15.10.26 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Mar 2011 15:10:28 -0700 (PDT) Message-ID: <4D7D40C8.3060707@googlemail.com> Date: Sun, 13 Mar 2011 22:10:00 -0000 From: Michael Zintakis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 MIME-Version: 1.0 To: Ian Lance Taylor 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> <4D7CD348.2060509@googlemail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/msg00136.txt.bz2 Ian, thanks for your response! >> /home/mz/gcc-test/gcc-build/./gcc/as: line 83: exec: : not found >> > > You must build and install a cross-binutils with the same --target and > --prefix option before you configure and build gcc. > I am a bit confused, I have to admit! It is true that I did use my own GCC compiler (on the host machine) to get the GCC2 built (skipping step one of the plan), so from what I gather from your response my host compiler needs to have all the binutils for the target platform installed as well, is that correct? Also, if I build GCC1 should I specify the different target platform I am interested in (ppc in my example) so that it could build its own binutils for that platform? Would that work? Following from the "Building a cross compiler" section it tells me that by issuing "make" it "Builds target tools for use by the compiler such as binutils (bfd, binutils, gas, gprof, ld, and opcodes) if they have been individually linked or moved into the top level GCC source tree before configuring." - what does that mean exactly I am unclear? The strange thing is that my host machine GCC already has i686 and x86_64 binutils installed (though as a "ready-made" package - I haven't compiled this from source so can't vouch for the correctness of these packages) and when I attempted to build GCC2 with "--target=i686-redhat-linux" it also failed! I know the host GCC on that machine works as I also do compilation for boh x86_64 and i686 arches successfully. Maybe I am missing something else.