GNU bug report logs -
#44636
Misleading documentation
Previous Next
Reported by: Robert Menteer <reetnem <at> mac.com>
Date: Sat, 14 Nov 2020 16:15:01 UTC
Severity: normal
Done: Jacob Bachmeyer <jcb62281 <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Tue, 17 Nov 2020 21:56:55 -0600
with message-id <5FB49B87.6070502 <at> gmail.com>
and subject line Re: bug#44636: Misleading documentation
has caused the debbugs.gnu.org bug report #44636,
regarding Misleading documentation
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
44636: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=44636
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
[Message part 3 (text/plain, inline)]
In section 4.2.2 of the info manual for DejaGnu it suggests to create a subdirectory config then create a tool init file in it. If I copy the unix.exp example to /…/testsuite/config/tool.exp runtool does not appear to read it. Looking around the web I found a mention of placing the init file in /…/testsuite/lib/. This does seem to work as I get the following output:
Using ./lib/FlDist.exp as tool init file.
Another problem with the example init file in that same section is the expect statement:
global ${examplename}
This causes the following error:
ERROR: tcl error sourcing tool init file ./lib/FlDist.exp.
can't read "examplename": no such variable
The problem with the documentation is not that it uses examplename in it’s example but there is nothing explaining how to modify examplename to fit the tool. This is in contrast to naming files which is explained in the manual.
Thanks,
Bob Menteer
[Message part 4 (text/html, inline)]
[Message part 5 (message/rfc822, inline)]
Robert Menteer via Bug-dejagnu via wrote:
> In section 4.2.2 of the info manual for DejaGnu it suggests to create
> a subdirectory config then create a tool init file in it. If I copy
> the unix.exp example to /…/testsuite/config/tool.exp runtool does not
> appear to read it.
You are correct that this is wrong; the manual is conflating tool init
files and target interface files here.
> Looking around the web I found a mention of placing the init file in
> /…/testsuite/lib/.
This is correct; the manual has been corrected in commit
9950000f4ec0f6cd2c5afbc8ec5413391c20a535.
Closing as now fixed.
-- Jacob
This bug report was last modified 4 years and 187 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.