From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12115 invoked by alias); 5 Oct 2009 13:38:28 -0000 Received: (qmail 12105 invoked by uid 22791); 5 Oct 2009 13:38:27 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-pz0-f181.google.com (HELO mail-pz0-f181.google.com) (209.85.222.181) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 05 Oct 2009 13:38:23 +0000 Received: by pzk11 with SMTP id 11so1505054pzk.14 for ; Mon, 05 Oct 2009 06:38:22 -0700 (PDT) Received: by 10.115.61.10 with SMTP id o10mr60368wak.37.1254749901945; Mon, 05 Oct 2009 06:38:21 -0700 (PDT) Received: from Paullaptop (124-170-16-182.dyn.iinet.net.au [124.170.16.182]) by mx.google.com with ESMTPS id 23sm1461381pzk.4.2009.10.05.06.38.18 (version=SSLv3 cipher=RC4-MD5); Mon, 05 Oct 2009 06:38:20 -0700 (PDT) Message-ID: From: "Paul Edwards" To: "Michael Matz" , "Ulrich Weigand" Cc: "Ian Lance Taylor" , References: <200909251516.n8PFGPYn014618@d12av02.megacenter.de.ibm.com><4F1842D6879348899E3A1999066969F5@Paullaptop><4AC39435.8010902@redhat.com><36D486ECFFC04FBD8318DFDD333FD206@Paullaptop><7AE4510479514D0E9B72A9B827275199@Paullaptop><77AE26D4B4604E1EB60B7B6152EA9FD4@Paullaptop> <01EDD002E9184163A5A91409025429D6@Paullaptop> In-Reply-To: Subject: Re: i370 port - constructing compile script Date: Mon, 05 Oct 2009 13:38:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-10/txt/msg00089.txt.bz2 > .../configure --target=i370-mvs --prefix=... --with-sysroot=... \ > --enable-languages=c Thanks Ulrich. That's very different from the concept I had of how the build process was meant to work. > Ignoring the cross stuff, if this is all you need I would suggest calling > make in the right way to generate this script. We'll use a fake > "compiler" for making cc1 which does nothing else than appending its > command line to your compile script. Hence, create a script > collect-stuff.sh with this content: > > -------- snip ---------- > #!/bin/sh > echo stdcomp ${1+"$@"} >> /tmp/compile > -------- snap ---------- > > Now we'll call make so that it only tries to make cc1 with this compiler > to collect the commands: > > % cd gcc > % make CC=collect-stuff.sh cc1 Thanks Michael. That's exactly the sort of thing I was after. Just one thing - I'll need more than cc1. I need the files that normally go into gcc as well. So a combination of those two sets of source, so that I can get a single standalone executable. So I'll need to create a new Makefile target that's a bit bigger than cc1. But cc1 will come close. Also, I decided that I'd better go back to gcc 3.4.6 in order to do this experimentation, because at least with that I know that at the end of the day, there's no compiler issue, so if it doesn't work, the fault must lie withe the build process. I can't say that about 4.4, because I already know a normally built cross-compiler on 4.4 with a resuscitated i370 will build, but has a runtime error which wasn't immediately obvious (ie gdb didn't point to something wrong). After 3.4.6 is working, I'll hopefully have an easier time with 4.4. Anyway, I'll try it out tomorrow etc, and report back the results. BFN. Paul.