From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6658 invoked by alias); 30 Dec 2003 08:26:34 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 6651 invoked from network); 30 Dec 2003 08:26:30 -0000 Received: from unknown (HELO granger.mail.mindspring.net) (207.69.200.148) by sources.redhat.com with SMTP; 30 Dec 2003 08:26:30 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by granger.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1AbFCt-0004Po-00; Tue, 30 Dec 2003 03:26:27 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 140414B35A; Tue, 30 Dec 2003 03:26:25 -0500 (EST) To: eliz@elta.co.il Subject: Re: [RFC] Fix compilation failure of remote-fileio.c Cc: gdb-patches@sources.redhat.com Message-Id: <20031230082625.140414B35A@berman.michael-chastain.com> Date: Tue, 30 Dec 2003 08:26:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2003-12/txt/msg00518.txt.bz2 Hi Eli, src/gdb/configure is produced with this version of autoconf: ftp://sources.redhat.com/pub/binutils/autoconf-000227.tar.bz2 This version of autoconf identifies itself as "autoconf version 2.13", but produces different "configure" files than autoconf 2.13. Fun fun fun! The difference is that autoconf-000227 has some "--site-file" stuff in it that I don't even understand. But that's the blessed version for gdb. eli> Because running Autoconf 2.13 installed on fencepost.gnu.org eli> produces quite a few errors about undefined macros. What am I missing? Oddly, when I run the real autoconf 2.13 on current cvs HEAD, it does run. It just produces a different "configure" than the version in cvs. autoconf 000227 produces the identical "configure". So if you are getting "undefined macros" then there is something even more wrong. I would recommend: -- download autoconf 000227 -- build your own private copy of it -- check that it generates identical "configure" Do that before banging on configure.in eli> Also, if it _is_ Autoconf 2.13, then it seems like it doesn't know eli> about AC_CHECK_MEMBER, so what should I put in configure.in for eli> testing the existence of st_blocks? Maybe cut-and-paste from the l_addr check? Michael C