bug-dejagnu
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-dejagnu] makeinfo fails on dejagnu.texi


From: Faraz Shahbazker
Subject: Re: [Bug-dejagnu] makeinfo fails on dejagnu.texi
Date: Thu, 7 Apr 2016 12:02:55 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0

More pointer errors.
Seems like the sectioning commands are already in place, maybe the next 
clean-up should just remove next/prev/up from all nodes.

Regards,
Faraz Shahbazker

Patch:
---
diff --git a/doc/dejagnu.texi b/doc/dejagnu.texi
index 5dddf13..6c92c51 100644
--- a/doc/dejagnu.texi
+++ b/doc/dejagnu.texi
@@ -991,11 +991,11 @@ command line.
 * Board config file::
 * Remote host testing::
 * Config file values::
 @end menu
 
address@hidden Global config file, Board config file, Local config file, 
Customizing DejaGnu
address@hidden Global config file, Local config file, , Customizing DejaGnu
 @section Global config file
 
 The global configuration file is where all the target specific
 configuration variables for a site are set. For example, a centralized
 testing lab where multiple developers have to share an embedded
@@ -1051,11 +1051,11 @@ using all possible combinations of the 
@code{--soft-float} and the
 @code{--el} (little endian) options.  The braced string includes an
 initial comma so that the set of combinations includes no options at
 all. Needless to say, this last target example is mostly specific to
 compiler testing.
 
address@hidden Local config file, Global config file, , Customizing DejaGnu
address@hidden Local config file, Board config file, Global config file, 
Customizing DejaGnu
 @section Local config file
 
 It is usually more convenient to keep these @emph{manual overrides} in
 the @file{site.exp} local to each test directory, rather than in the
 global @file{site.exp} in the installed DejaGnu library. This file is



reply via email to

[Prev in Thread] Current Thread [Next in Thread]