From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11572 invoked by alias); 1 Oct 2009 14:00:14 -0000 Received: (qmail 11552 invoked by uid 22791); 1 Oct 2009 14:00: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-px0-f191.google.com (HELO mail-px0-f191.google.com) (209.85.216.191) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 01 Oct 2009 14:00:05 +0000 Received: by pxi29 with SMTP id 29so166400pxi.14 for ; Thu, 01 Oct 2009 07:00:03 -0700 (PDT) Received: by 10.114.2.29 with SMTP id 29mr2115925wab.48.1254405603204; Thu, 01 Oct 2009 07:00:03 -0700 (PDT) Received: from Paullaptop (124-170-16-182.dyn.iinet.net.au [124.170.16.182]) by mx.google.com with ESMTPS id 23sm50037pzk.0.2009.10.01.06.59.59 (version=SSLv3 cipher=RC4-MD5); Thu, 01 Oct 2009 07:00:01 -0700 (PDT) Message-ID: <3E8D7C3EE697451A9DD12720F287E2CD@Paullaptop> From: "Paul Edwards" To: "Joseph S. Myers" , "Ian Lance Taylor" Cc: "Richard Henderson" , References: <200909251516.n8PFGPYn014618@d12av02.megacenter.de.ibm.com> <4F1842D6879348899E3A1999066969F5@Paullaptop> <4AC39435.8010902@redhat.com> <36D486ECFFC04FBD8318DFDD333FD206@Paullaptop> In-Reply-To: Subject: Re: i370 port - constructing compile script Date: Thu, 01 Oct 2009 14:00: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/msg00010.txt.bz2 >> > 2. If the normal way to do things is to parse the make -n output >> > with perl etc, that's fine, I'll do it that way. I was just wondering >> > if the proper way was to incorporate the logic into a Makefile >> > rule and get that rule repeatedly executed rather than just >> > having a simple "echo". It seems to me that having a generic >> > rule to execute an external script would be neater??? >> >> I'm not sure what you are suggesting here, but I do know that it >> wouldn't make sense for us to change the gcc Makefile to use a rule >> which executes an external script. I didn't mean use by default. >> The "normal way to do things" is to use GNU make. I think you are the >> first person trying to build gcc without it. It's also the first native MVS port. Anyway, since then I had another idea. I should be able to achieve the same thing by just changing the C compiler to be "echo" or the external script replacement. Then all I need is a consolidated stage 1 target. But today I spent my time fighting a different battle. I tried to get configure to use my provided minimal (ie all of C90, but no extensions) header files, using the --with-root option and --with-build-root. But it seemed to ignore those and use the ones on my Linux box, insisting that sys/types existed etc. Maybe I need to change my INCLUDE_PATH or something instead. > Not the first - BSDs have been known to import GCC sources into their > repositories and write their own build system using BSD make. No doubt > this is a lot of work that needs repeating for each new version imported - > that's the price you pay if you don't want to use the normal GCC build > system. > (And GCC didn't always require GNU make - but the BSDs replacing the build > system are a much closer analogy here than ordinary builds of old versions > with other make implementations before GNU make was required.) Yeah, make isn't available (environment variables aren't available in batch either), and even if it was, that's not what people want. People want SMP/E in fact. But I don't know SMP/E. I only know JCL, which is the normal (and much much simpler) rival for SMP. I don't think that doing a glorified "make -n" is a radical change to the existing methodology. Nor is a make target that just lists all the stage 1 object files. I think it would be a neat addition (even if it remains a patch forever). BFN. Paul.