X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Received: by 2002:a5d:588a:0:b0:1e8:b478:e74f with SMTP id n10-20020a5d588a000000b001e8b478e74fmr22675014wrf.210.1645607642484;
        Wed, 23 Feb 2022 01:14:02 -0800 (PST)
X-Received: by 2002:a0d:cc49:0:b0:2d1:5167:ed08 with SMTP id
 o70-20020a0dcc49000000b002d15167ed08mr27319514ywd.114.1645607641984; Wed, 23
 Feb 2022 01:14:01 -0800 (PST)
Newsgroups: comp.os.msdos.djgpp
Date: Wed, 23 Feb 2022 01:14:01 -0800 (PST)
In-Reply-To: <838ru2tg43.fsf@gnu.org>
Injection-Info: google-groups.googlegroups.com; posting-host=5.12.19.194; posting-account=W7Xq4AoAAACdWdBRi2rb45ZV3AtecYoa
NNTP-Posting-Host: 5.12.19.194
References: <b84357c3-50cd-4b14-b88a-d55bdc8c58d1n AT googlegroups DOT com>
 <83a6eiu2dt DOT fsf AT gnu DOT org> <11cd86a4-05c0-4263-9cfc-ba6092388807n AT googlegroups DOT com>
 <838ru2tg43 DOT fsf AT gnu DOT org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <d88f70e8-26c0-4c46-b835-7bb34e735e35n@googlegroups.com>
Subject: Re: Menu reference to nonexistent node error
From: "Khusraw (mv DOT ionascu AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Injection-Date: Wed, 23 Feb 2022 09:14:02 +0000
Content-Type: text/plain; charset="UTF-8"
Bytes: 1924
Lines: 9
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Then you need to investigate why: this is the problem, AFAIR. This 
> file should have the entire contents of the manual, generated from all 
> the *.txh files spread all over the source tree.

Unfortunately I don't have time for such investigations, I thought that if I have all the 
latest required DJGPP packages installed and run "make" everything is built without
problems (the error appears in both NTVDM and DOSBox, the only "systems" I have
available for building). But I noticed something else, if I run "mkdoc . libc2.tex" 
outside the building process, libc2.tex is correctly generated and the building process 
continues with no more errors.