From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2996 invoked by alias); 28 Oct 2003 22:00:55 -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 2988 invoked from network); 28 Oct 2003 22:00:55 -0000 Received: from unknown (HELO zenia.home) (12.223.225.216) by sources.redhat.com with SMTP; 28 Oct 2003 22:00:55 -0000 Received: by zenia.home (Postfix, from userid 5433) id 50A7F207AF; Tue, 28 Oct 2003 16:59:58 -0500 (EST) To: Eli Zaretskii Cc: gdb-patches@sources.redhat.com Subject: Re: RFA: fix node name (revised patch) References: <9003-Sat25Oct2003145827+0200-eliz@elta.co.il> From: Jim Blandy Date: Tue, 28 Oct 2003 22:00:00 -0000 In-Reply-To: <9003-Sat25Oct2003145827+0200-eliz@elta.co.il> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-10/txt/msg00821.txt.bz2 "Eli Zaretskii" writes: > > From: Jim Blandy > > Date: 24 Oct 2003 22:59:39 -0500 > > > > I was trying to figure out why this hasn't bothered anyone yet --- the > > node name with the single quotes has been in there for months --- and > > I realized that it is because I'm using an older version of > > texinfo.tex (circa 1999). > > The real question that we should ask ourselves wrt this is: how come > your older texinfo.tex was being used instead of the one that comes > with GDB (which, I hope, is new enough). > > Can you look into this, please? The reason I'm getting an old texinfo.tex is that I'm building in a source tree produced by checking out a module from Red Hat's internal CVS repository that excludes texinfo --- the module contains only cross-compilation tools, assuming that the user has an appropriate native toolchain installed on his system already. Specifically, it does not contain its own texinfo directory. So the build gets the texinfo.tex installed as part of Red Hat 8.0, which says: \def\texinfoversion{1999-09-25.10} So there is no underlying problem in GDB's documentation build process; it is an anomaly introduced by our internal processes.