From fant@pobox.com Mon Jun 27 09:02:07 2005 Received: with ECARTIS (v1.0.0; list pcp); Mon, 27 Jun 2005 09:02:12 -0700 (PDT) Received: from fuse1.fusemail.net (smtp.fusemail.net [69.31.1.141]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j5RG27H9026103 for ; Mon, 27 Jun 2005 09:02:07 -0700 Received: from fusemail.com by fuse1.fusemail.net with asmtp (TLSv1:AES256-SHA:256) (FuseMail extSMTP) id 1Dmw2F-0002rT-Jn for pcp@oss.sgi.com; Mon, 27 Jun 2005 11:00:35 -0500 Message-ID: <42C022A4.9030107@pobox.com> Date: Mon, 27 Jun 2005 12:00:36 -0400 From: "Andrew D. Fant" User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050329) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pcp@oss.sgi.com Subject: makefile stomps on ./configure options X-Enigmail-Version: 0.90.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-archive-position: 437 X-ecartis-version: Ecartis v1.0.0 Sender: pcp-bounce@oss.sgi.com Errors-to: pcp-bounce@oss.sgi.com X-original-sender: fant@pobox.com Precedence: bulk X-list: pcp Content-Length: 436 Lines: 9 In the course of trying to build 2.4.0 on a system here, I noticed some strange behavior. After running configure with some options set to conform to local layout standards, it appears that the first thing the makefile does is to rerun configure with no variables set at all. Is there a reason for this, and if so, is there a recommended workaround that doesn't require manual repatching of the makefile at each build? Thanks, Andy From kenmcd@melbourne.sgi.com Wed Jun 29 13:18:53 2005 Received: with ECARTIS (v1.0.0; list pcp); Wed, 29 Jun 2005 13:18:55 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j5TKIpH9016621 for ; Wed, 29 Jun 2005 13:18:52 -0700 Received: from ppp-kenmcd.melbourne.sgi.com (ppp-kenmcd.melbourne.sgi.com [134.14.52.219]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id GAA29327; Thu, 30 Jun 2005 06:17:15 +1000 Date: Thu, 30 Jun 2005 06:15:27 +1000 (EST) From: kenmcd@melbourne.sgi.com Reply-To: Ken McDonell To: "Andrew D. Fant" cc: pcp@oss.sgi.com Subject: Re: makefile stomps on ./configure options In-Reply-To: <42C022A4.9030107@pobox.com> Message-ID: References: <42C022A4.9030107@pobox.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-archive-position: 438 X-ecartis-version: Ecartis v1.0.0 Sender: pcp-bounce@oss.sgi.com Errors-to: pcp-bounce@oss.sgi.com X-original-sender: kenmcd@melbourne.sgi.com Precedence: bulk X-list: pcp Content-Length: 1168 Lines: 23 On Mon, 27 Jun 2005, Andrew D. Fant wrote: > In the course of trying to build 2.4.0 on a system here, I noticed some > strange behavior. After running configure with some options set to > conform to local layout standards, it appears that the first thing the > makefile does is to rerun configure with no variables set at all. Is > there a reason for this, and if so, is there a recommended workaround > that doesn't require manual repatching of the makefile at each build? Hmm ... the problem here was that for some platforms, we may have autoconf in _our_ build environment, but this may be uncommon for others ... so we opted to ship a configure, but over time the top-level GNUmakefile has evolved (regressed?) to the point where it unconditionally tries to remake configure. It needs some minor tweaking to include configure.default (or similar) instead of configure in the distribution for a specific platform, and then use that if autoconf is not available and congigure cannot be regenerated from configure.in ... I'll do this when I get a chance (don't hold your breath), or I'd be glad to accept a patch to this effect. Thanks for pointing this out.