From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20072 invoked by alias); 18 Jan 2010 03:38:24 -0000 Received: (qmail 20063 invoked by uid 22791); 18 Jan 2010 03:38:23 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 18 Jan 2010 03:38:19 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id C429D2BAB35; Sun, 17 Jan 2010 22:38:17 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KPgBftfenqNA; Sun, 17 Jan 2010 22:38:17 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 377022BAB0C; Sun, 17 Jan 2010 22:38:17 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 28647F5970; Mon, 18 Jan 2010 07:38:04 +0400 (RET) Date: Mon, 18 Jan 2010 03:38:00 -0000 From: Joel Brobecker To: Jie Zhang Cc: gdb-patches@sourceware.org Subject: Re: [RFA] Fix a parallel build error in doc Message-ID: <20100118033804.GB17397@adacore.com> References: <4B5262AC.3080606@analog.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B5262AC.3080606@analog.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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 X-SW-Source: 2010-01/txt/msg00435.txt.bz2 > We should also add GDBvn.texi in ANNOTATE_DOC_BUILD_INCLUDES, shouldn't we? > > Is the attached patch OK? Actually, it is gdb-cfg.texi that includes GDBvn.texi, not annotate.texinfo. So a better fix is to add that dependency to gdb-cfg.texi, no? It's kind of borderline, since one can create gdb-cfg.texi without GDBvn.texi. However, on the other hand, it makes it simpler for the other documents that depend on gdb-cfg.texi, as they do not have to know that gdb-cfg.texi depends on GDBvn.texi (and possibly other files too). -- Joel