From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2921 invoked by alias); 6 Oct 2009 09:32:12 -0000 Received: (qmail 2912 invoked by uid 22791); 6 Oct 2009 09:32:12 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-pz0-f203.google.com (HELO mail-pz0-f203.google.com) (209.85.222.203) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 06 Oct 2009 09:32:06 +0000 Received: by pzk41 with SMTP id 41so2051847pzk.0 for ; Tue, 06 Oct 2009 02:32:05 -0700 (PDT) Received: by 10.114.250.2 with SMTP id x2mr2043001wah.7.1254821525009; Tue, 06 Oct 2009 02:32:05 -0700 (PDT) Received: from Paullaptop (124-170-16-182.dyn.iinet.net.au [124.170.16.182]) by mx.google.com with ESMTPS id 23sm1996737pzk.4.2009.10.06.02.32.01 (version=SSLv3 cipher=RC4-MD5); Tue, 06 Oct 2009 02:32:03 -0700 (PDT) Message-ID: From: "Paul Edwards" To: "Ulrich Weigand" Cc: "Ian Lance Taylor" , References: <200910051315.n95DF2Gd023159@d12av02.megacenter.de.ibm.com> In-Reply-To: <200910051315.n95DF2Gd023159@d12av02.megacenter.de.ibm.com> Subject: Re: i370 port - constructing compile script Date: Tue, 06 Oct 2009 09:32: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/msg00106.txt.bz2 >> Would you be able to give me the two suggested configure >> commands so that I can find out the answer to the above, one >> way or another? > > For step 2 (building the cross-compiler), you'd need something > along the lines of > > .../configure --target=i370-mvs --prefix=... --with-sysroot=... \ > --enable-languages=c > > where prefix points to the directory where the cross-compiler > should be installed, and sysroot points to the directory where > the MVS libraries and header are installed. I tried to action this today. But first I tried to get the normal make process working, ie without the --prefix and --with-sysroot above, and just using defaults. I had some surprising success, but also one failure. The failure (on 3.4.6, but not on 3.2.3) is that after the successful build, when I do an xgcc -S, it produces the assembler file, and then hangs. I traced this to gcc.c which was in a loop doing this: pid = pwait (commands[i].pid, &status, 0); getting a return of 0 all the time, while the process (cc1) that it is waiting on is showing up as being . Not sure what that is about. I have gcc 3.2.3 working without that problem, so I'll spend some time comparing how the two pexecutes work differently. Of course I don't have system-related problems like this on MVS, because I have a single executable and a simple function call. :-) In the meantime, I have a question. You said above that I have to point sysroot to the MVS libraries and headers. What libraries? And why, at the point of building a cross-compiler, do I need any of those things? The normal way I build a cross-compiler I just do the above configure without prefix or with-sysroot, and it builds an xgcc executable as expected, using the Linux headers, as expected. I would certainly like an option to force it to use my C90-only Linux headers and my C90-only libraries, but that should be strictly optional, and if I did do that, I would expect to see configure saying things like "no you don't have fork, or getrusage, or sys/types" etc etc. I think I am still failing to understand some major aspect of the build process. BFN. Paul.