From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1863 invoked by alias); 12 Nov 2009 20:06:08 -0000 Received: (qmail 1855 invoked by uid 22791); 12 Nov 2009 20:06:08 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail.gmx.net (HELO mail.gmx.net) (213.165.64.20) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Thu, 12 Nov 2009 20:06:02 +0000 Received: (qmail invoked by alias); 12 Nov 2009 20:05:59 -0000 Received: from xdsl-87-78-91-97.netcologne.de (EHLO localhost.localdomain) [87.78.91.97] by mail.gmx.net (mp006) with SMTP; 12 Nov 2009 21:05:59 +0100 Received: from ralf by localhost.localdomain with local (Exim 4.69) (envelope-from ) id 1N8fvZ-0006XX-O4; Thu, 12 Nov 2009 21:05:57 +0100 Date: Thu, 12 Nov 2009 20:06:00 -0000 From: Ralf Wildenhues To: Paul Edwards Cc: Ulrich Weigand , Ian Lance Taylor , gcc@gcc.gnu.org Subject: Re: i370 port - constructing compile script Message-ID: <20091112200557.GB25110@gmx.de> Mail-Followup-To: Ralf Wildenhues , Paul Edwards , Ulrich Weigand , Ian Lance Taylor , gcc@gcc.gnu.org References: <200910191419.n9JEJcvD023336@d12av02.megacenter.de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-08-09) X-IsSubscribed: yes 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-11/txt/msg00362.txt.bz2 Hello Paul, * Paul Edwards wrote on Thu, Nov 12, 2009 at 03:02:59PM CET: > Well, I have good news to report. The restructuring was a success. > > That means with those 30-odd changes to the configure scripts, I > was able to get an auto-host.h built that allowed me to take the > generated source and compile it with my own scripts as per > normal. It would be a good idea if you took the extra mile and reported all these changes to the bug-autoconf mailing list, so it could be fixed for good there. Furthermore, it would be really good if we could get Autoconf to build and run on your system, so you could run its test suite there. That would provide much better coverage of all the issues that would need fixing, and allow us to fix them once in the macros, instead of having you do this repeatedly in every configure script. However, Autoconf requires Perl and GNU M4 (and some shell environment as well as a make program), so I'm not sure whether it is possible to get to this point. Thanks, Ralf