From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17326 invoked by alias); 27 Oct 2009 12:03:14 -0000 Received: (qmail 17250 invoked by uid 22791); 27 Oct 2009 12:03:13 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-px0-f176.google.com (HELO mail-px0-f176.google.com) (209.85.216.176) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 27 Oct 2009 12:03:04 +0000 Received: by pxi6 with SMTP id 6so44094pxi.0 for ; Tue, 27 Oct 2009 05:03:02 -0700 (PDT) Received: by 10.114.165.35 with SMTP id n35mr1067054wae.183.1256644982618; Tue, 27 Oct 2009 05:03:02 -0700 (PDT) Received: from Paullaptop (203-214-142-52.perm.iinet.net.au [203.214.142.52]) by mx.google.com with ESMTPS id 23sm200812pxi.13.2009.10.27.05.02.59 (version=SSLv3 cipher=RC4-MD5); Tue, 27 Oct 2009 05:03:00 -0700 (PDT) Message-ID: <2F7AC157ED03461F97454F8675AA4F75@Paullaptop> From: "Paul Edwards" To: "Ulrich Weigand" Cc: "Ulrich Weigand" , References: <200910240228.n9O2SYAV011735@d12av02.megacenter.de.ibm.com> In-Reply-To: <200910240228.n9O2SYAV011735@d12av02.megacenter.de.ibm.com> Subject: Re: i370 port - constructing compile script Date: Tue, 27 Oct 2009 12:18: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/msg00548.txt.bz2 > This means that if your GCC source tree resides in a directory, say, > ~/gcc-src > you should *not* run ./configure while in ~/gcc-src. Instead, you > should create a second, empty directory > ~/gcc-build > (which is not a subdirectory of ~/gcc-src), and run > ../gcc-src/configure ... > while in ~/gcc-build. Ok, I tried that, and it still didn't fix the problem. Not only that, after I fixed the problem (below), I ended up getting an error that way. input.h not found or something like that. So I went back to the source tree build, and made quite a lot of progress. First of all, the problem was obvious in hindsight. I had commented out a whole lot of stuff in configure in order to stop things from being auto-detected. However, that was interfering with the configure for the build environment!!! So I put #if !defined(__MVS__) around everything that I was commenting out, and I was able to get past genmodes and on to the next error. The next error was that it was trying to use ino_t in a header file, which doesn't exist. The way I got around this using my own procedure was to create a unixio.h which has the various Posix stuff in it. E.g. I have an open() that calls fopen(). ino_t is one of the typedefs there. Anyway, I put a #include "unixio.h" into config.h and got past that problem. I don't think that was the right thing to do though, because that is a generated file. What should I have done instead? A #include of "config/i370/mvspdp.h" got around the next problem, and I think I need to do more investigation as to why that was needed. Then finally I ran into an internal compiler error which I haven't seen before. One of the gcc options must have triggered something off. Perhaps it was -Wwrite-strings, or maybe the -O2 (I normally use -Os for a completely unrelated reason). Either way, I need to find out how to switch off those flags. I'll also try to fix the compiler internal error in i370.md. BFN. Paul.