From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15797 invoked by alias); 28 May 2003 14:19:54 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 15786 invoked from network); 28 May 2003 14:19:54 -0000 Received: from unknown (HELO crack.them.org) (146.82.138.56) by sources.redhat.com with SMTP; 28 May 2003 14:19:54 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 19L1n1-0001QF-00; Wed, 28 May 2003 09:20:27 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 19L1mO-0000Fu-00; Wed, 28 May 2003 10:19:48 -0400 Date: Wed, 28 May 2003 14:19:00 -0000 From: Daniel Jacobowitz To: Klaus Zeitler Cc: gdb@sources.redhat.com Subject: Re: problems building CVS snapshot Message-ID: <20030528141948.GB906@nevyn.them.org> Mail-Followup-To: Klaus Zeitler , gdb@sources.redhat.com References: <20030527142251.GA10062@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2003-05/txt/msg00364.txt.bz2 On Wed, May 28, 2003 at 03:49:54PM +0200, Klaus Zeitler wrote: > >>>>> "Daniel" == Daniel Jacobowitz writes: > > >> 1. configure complains about sys/ptem.h > >> > >> checking sys/ptem.h usability... no > >> checking sys/ptem.h presence... yes > >> configure: WARNING: sys/ptem.h: present but cannot be compiled > >> configure: WARNING: sys/ptem.h: check for missing prerequisite headers? > >> configure: WARNING: sys/ptem.h: proceeding with the preprocessor's result > >> configure: WARNING: ## ------------------------------------ ## > >> configure: WARNING: ## Report this to bug-autoconf@gnu.org. ## > >> configure: WARNING: ## ------------------------------------ ## > >> > >> a test C program that additionally contains sys/streams.h does compile. > >> > >> I reported this yesterday to bug-autoconf and got the following reply: > Daniel> > Daniel> Thanks for the report. I'll hold on to this, since we are going > Daniel> to be transitioning to autoconf 2.5x at some point, but this is > Daniel> actually a problem with your setup. We only support autoconf 2.13. > > I've now installed autoconf 2.13 and get the same message Make sure you rebuilt the affected configures with the older autoconf. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer