From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23595 invoked by alias); 21 Aug 2014 15:00:39 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 23585 invoked by uid 89); 21 Aug 2014 15:00:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.3.2 X-HELO: mtaout26.012.net.il Received: from mtaout26.012.net.il (HELO mtaout26.012.net.il) (80.179.55.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 21 Aug 2014 15:00:37 +0000 Received: from conversion-daemon.mtaout26.012.net.il by mtaout26.012.net.il (HyperSendmail v2007.08) id <0NAN00000W2J9900@mtaout26.012.net.il> for gdb-patches@sourceware.org; Thu, 21 Aug 2014 17:58:58 +0300 (IDT) Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout26.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NAN00FACWAABOA0@mtaout26.012.net.il>; Thu, 21 Aug 2014 17:58:58 +0300 (IDT) Date: Thu, 21 Aug 2014 15:00:00 -0000 From: Eli Zaretskii Subject: Re: [doc] Avoid conflicts between gdb and cross-gdb. In-reply-to: <53F6018E.7020302@redhat.com> To: Pedro Alves Cc: vapier@gentoo.org, brobecker@adacore.com, dje@google.com, gdb-patches@sourceware.org, monaka@monami-software.com Reply-to: Eli Zaretskii Message-id: <83oavdc2ge.fsf@gnu.org> References: <20140806213412.GD4881@adacore.com> <8361i4nw49.fsf@gnu.org> <1554189.EX2Nlz1ClI@vapier> <53F6018E.7020302@redhat.com> X-IsSubscribed: yes X-SW-Source: 2014-08/txt/msg00483.txt.bz2 > Date: Thu, 21 Aug 2014 15:26:22 +0100 > From: Pedro Alves > CC: Joel Brobecker , dje@google.com, > gdb-patches@sourceware.org, monaka@monami-software.com > > > yes, you'd actually have to rewrite the base node name so that instead of > > identifying itself as "gdb" it'd be "${target}-gdb" (i.e. apply the program > > transformation). then doing `info sh4-linux-gnu-gdb` would give you the > > correct man page. this matches the man page behavior where you can do `man > > sh4-linux-gnu-gdb` and such. > > Eh, I always assumed this sort of thing is why we write @value{GDBN} all > over the manual, and that we were already transforming that, but indeed > seems like we aren't. In addition, we would need to use @value{GDBN} in the @direntry section of gdb.texinfo.