From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11979 invoked by alias); 14 Mar 2011 01:47:11 -0000 Received: (qmail 11970 invoked by uid 22791); 14 Mar 2011 01:47:09 -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-fx0-f47.google.com (HELO mail-fx0-f47.google.com) (209.85.161.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 14 Mar 2011 01:47:05 +0000 Received: by fxm19 with SMTP id 19so2443476fxm.20 for ; Sun, 13 Mar 2011 18:47:03 -0700 (PDT) Received: by 10.223.79.14 with SMTP id n14mr2165095fak.113.1300067223184; Sun, 13 Mar 2011 18:47:03 -0700 (PDT) Received: from [127.0.0.1] ([46.28.108.24]) by mx.google.com with ESMTPS id n26sm2807807fam.13.2011.03.13.18.46.57 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Mar 2011 18:47:01 -0700 (PDT) Message-ID: <4D7D738C.2010407@googlemail.com> Date: Mon, 14 Mar 2011 01:47: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> <4D7D40C8.3060707@googlemail.com> <4D7D666C.8010400@googlemail.com> <4D7D6FAA.70302@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/msg00143.txt.bz2 >> Thanks! Downloaded along with mpfr, ppl-0.11.2 (configure said that my >> existing version is "buggy" :-) ) and cloog-ppl-0.15.9. >> >> If I dump mpfr, ppl and cloog-ppl in the main gcc source directory >> (and name those directories like that - "mpfr", "ppl" and "cloog-ppl") >> would that be enough for the GCC build or do I have to compile/install >> them separately? >> > > As far as I know that is fine. I haven't done much with PPL myself. > It says on the gcc pre-requisite pages that these packages are good for doing the optimisations, so I thought there is no harm to include these in the build as well. I'll try them when I do my 2nd pass. Currently I took the plunge and dumped the whole binutils directory in the main gcc source...will see how it goes after I selected --host=x86_64 and --target=powerpc, fingers crossed! >> If I copy binutils sources to the main gcc source directory what would >> be the sign that they are incompatible - the same error as I was >> getting before (line 83 etc)? >> > > No, the errors are much more subtle. I really can't encourage this > unless you are prepared to investigate and solve problems yourself. > I hope there is no conflict, but if there is and I get an error I will build binutils separately. >>> What do you see in the config.log file? >>> >>> >> The same one I was getting with the ppc target - line 83 etc etc. >> > > I'm sorry, I don't recall what that was. If it's a missing 'as' file > then the simple answer is still going to be to install the binutils. At > one time gcc would fall back to running 'as' even for a cross-compiler, > but perhaps that is no longer the case. > I am a bloody moron! I forgot to rename the mpfr directory when dumping the source and this was the reason for the build to stop midway through - it is OK now, I just compiled GCC with the multilib option on without any glitches. We're getting there!!! MZ