From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21091 invoked by alias); 1 Oct 2009 14:28:19 -0000 Received: (qmail 21079 invoked by uid 22791); 1 Oct 2009 14:28:19 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_FAIL X-Spam-Check-By: sourceware.org Received: from mx20.gnu.org (HELO mx20.gnu.org) (199.232.41.8) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 01 Oct 2009 14:28:15 +0000 Received: from [65.74.133.4] (helo=mail.codesourcery.com) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MtMdh-0000Gr-OI for gcc@gcc.gnu.org; Thu, 01 Oct 2009 10:28:14 -0400 Received: (qmail 24590 invoked from network); 1 Oct 2009 14:28:12 -0000 Received: from unknown (HELO wren.localnet) (paul@127.0.0.2) by mail.codesourcery.com with ESMTPA; 1 Oct 2009 14:28:12 -0000 From: Paul Brook To: gcc@gcc.gnu.org Subject: Re: i370 port - constructing compile script Date: Thu, 01 Oct 2009 14:28:00 -0000 User-Agent: KMail/1.12.1 (Linux/2.6.30-1-amd64; KDE/4.3.1; x86_64; ; ) Cc: "Paul Edwards" References: <200909251516.n8PFGPYn014618@d12av02.megacenter.de.ibm.com> <4F1842D6879348899E3A1999066969F5@Paullaptop> In-Reply-To: <4F1842D6879348899E3A1999066969F5@Paullaptop> MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Message-Id: <200910011528.11586.paul@codesourcery.com> X-detected-operating-system: by mx20.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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/msg00012.txt.bz2 > I am happy to construct all of this on a Unix system with the various > tools (m4 etc) available. > > But from the Unix system, I need to be able to generate the > above very simple compile script, which is a precursor to creating > very simple JCL steps (trust me, you don't want to see what > ST2CMP looks like). Note that the JCL has the filenames > truncated to 8 characters, listed twice, uppercased, and '-' > and '_' converted to '@'. Have you considered the obvious solution: Don't do that? i.e. use a cross compiler from a sane system. If you really want to a native compiler than I still suggest building it as a canadian cross. My guess is that getting gcc hosted in a bizarre environment is much easier than getting the gcc build system working. Trying to bootstrap gcc there seems like a lot of pain for no real benefit. Paul