From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29447 invoked by alias); 7 Dec 2002 20:50:31 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 29439 invoked from network); 7 Dec 2002 20:50:30 -0000 Received: from unknown (HELO lacrosse.corp.redhat.com) (66.187.233.200) by sources.redhat.com with SMTP; 7 Dec 2002 20:50:30 -0000 Received: from free.redhat.lsd.ic.unicamp.br (aoliva2.cipe.redhat.com [10.0.1.156]) by lacrosse.corp.redhat.com (8.11.6/8.9.3) with ESMTP id gB7KnoN18109; Sat, 7 Dec 2002 15:49:50 -0500 Received: from free.redhat.lsd.ic.unicamp.br (localhost.localdomain [127.0.0.1]) by free.redhat.lsd.ic.unicamp.br (8.12.5/8.12.5) with ESMTP id gB7Knnab030951; Sat, 7 Dec 2002 18:49:49 -0200 Received: (from aoliva@localhost) by free.redhat.lsd.ic.unicamp.br (8.12.5/8.12.5/Submit) id gB7KnmGB030947; Sat, 7 Dec 2002 18:49:48 -0200 To: Zack Weinberg Cc: Nathanael Nerode , gdb-patches@sources.redhat.com, binutils@sources.redhat.com, newlib@sources.redhat.com, gcc@gcc.gnu.org Subject: Re: [RFC] Update to current automake/autoconf/libtool versions. References: <20021205223538.GA24616@doctormoo> <87adjk83ce.fsf@egil.codesourcery.com> From: Alexandre Oliva Organization: GCC Team, Red Hat Date: Sat, 07 Dec 2002 12:55:00 -0000 In-Reply-To: <87adjk83ce.fsf@egil.codesourcery.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-12/txt/msg00398.txt.bz2 On Dec 5, 2002, Zack Weinberg wrote: > AC_NO_EXECUTABLES has two effects: (1) it disables the equivalent of > AC_PROG_CC_WORKS, which is what we need. But, (2) it causes autoconf > to barf if an AC_TRY_LINK test appears anywhere in the script being > generated. Please tell me why (2) doesn't make sense. If AC_PROG_CC_WORKS can't even link a do-nothing program, how would you expect to get any useful results from AC_TRY_LINK? > libstdc++-v3/configure.in has lots of AC_TRY_LINK tests. If we know AC_PROG_CC_WORKS fails, it is a mistake to use AC_TRY_LINK tests. Removing the constraint from autoconf will do us no good. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org} CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Free Software Evangelist Professional serial bug killer