* debian/control: Fix problem with "no binary package" error.
* debian/rules: Fix so things actually build a package. This was
mostly installing the new html version of the doc, not an info
page.
* doc/Makefile.am: Build and install the rtf and ps versions
of the manual. Remove all the created files and subdirectories.
* doc/overview.sgml: Update the copyright message.
* doc/ref.sgml: Update the copyright messages. Add section on
obtaining DejaGnu releases.
* doc/user.sgml: Update the copyright messages. Add blurb about
the --mail option.
* doc/overview: Regenerated.
+2001-02-21 Rob Savoye <rob@slipknot.welcomehome.org>
+
+ * debian/changelog: Add entry for new release.
+ * debian/control: Fix problem with "no binary package" error.
+ * debian/rules: Fix so things actually build a package. This was
+ mostly installing the new html version of the doc, not an info
+ page.
+ * doc/Makefile.am: Build and install the rtf and ps versions
+ of the manual. Remove all the created files and subdirectories.
+ * doc/overview.sgml: Update the copyright message.
+ * doc/ref.sgml: Update the copyright messages. Add section on
+ obtaining DejaGnu releases.
+ * doc/user.sgml: Update the copyright messages. Add blurb about
+ the --mail option.
+ * doc/overview: Regenerated.
+
2001-02-17 Rob Savoye <rob@slipknot.welcomehome.org>
* Most all files: Update copyright notices.
+dejagnu (1.4-0) stable; urgency=low
+ * Make this work again for the new release.
+
+ -- Rob Savoye <rob@welcomehome.org> Wed, 21 Feb 2001 04:37:07 -0800
+
dejagnu (1.3-10) frozen unstable; urgency=low
* add example to /usr/doc (fixes bug #28491)
Source: dejagnu
Section: devel
Priority: optional
-Maintainer: Kevin Dalley <kevind@rahul.net>
+Maintainer: Rob Savoye <welcomehome.org>
Standards-Version: 2.5.0.0
-Package: dejagnu-1.4
+
+Package: dejagnu
Architecture: all
Depends: expect, dpkg (>=1.2.1)
Description: framework for running test suites on software tools.
set -i
-install-info --quiet --section "Development" "Development" \
- /usr/info/dejagnu.info.gz
+#install-info --quiet --section "Development" "Development" \
+#/usr/doc/dejagnu.info.gz
-echo "Edit the master configuration file, /etc/dejagnu/site.exp,"
-echo "if needed"
+echo "Edit the master configuration file, /etc/dejagnu/site.exp, if needed"
install -d debian/tmp debian/tmp/DEBIAN
install -d debian/tmp/usr/doc/$(package)
install -d -g root -m 755 -o root debian/tmp/etc/$(package)
- install debian/{postinst,postrm,preinst,prerm} debian/tmp/DEBIAN/.
+ install debian/{postinst,preinst} debian/tmp/DEBIAN/.
cd $(package); $(MAKE) CC="$(CC)" CFLAGS="$(CFLAGS)" \
LDFLAGS="$(LDFLAGS)" \
- prefix=`pwd`/../debian/tmp/usr install
- chmod 0644 debian/tmp/usr/lib/dejagnu/runtest.exp
+ prefix=`pwd`/debian/tmp/usr install
+ chmod 0644 debian/tmp/usr/share/dejagnu/runtest.exp
cd $(package); $(MAKE) CC="$(CC)" CFLAGS="$(CFLAGS)" \
LDFLAGS="$(LDFLAGS)" \
- prefix=`pwd`/../debian/tmp/usr install-info
- gzip -9v debian/tmp/usr/info/*
- gzip -9v debian/tmp/usr/man/man1/*
+ pkgdatadir=debian/tmp/usr/doc/$(package) install-doc
+# gzip -9v debian/tmp/usr/info/*
+# gzip -9v debian/tmp/usr/man/man1/*
+ install -d debian/tmp/usr/doc/$(package)/html/stylesheet-images
+ install -m 0644 doc/overview.rtf debian/tmp/usr/doc/$(package)
+ install -m 0644 doc/overview.ps debian/tmp/usr/doc/$(package)
+ install -m 0644 doc/overview/*.html debian/tmp/usr/doc/$(package)/html
+ install -m 0644 doc/overview/stylesheet-images/*.png debian/tmp/usr/doc/$(package)/html/stylesheet-images
install -m 0644 debian/copyright debian/tmp/usr/doc/$(package)
install -m 0644 debian/changelog debian/tmp/usr/doc/$(package)/changelog.Debian
gzip -9v debian/tmp/usr/doc/$(package)/changelog.Debian
install -g root -m 644 -o root debian/site.exp \
debian/tmp/etc/$(package)/site.exp
cd debian/tmp/usr/lib/$(package); ln -fs /etc/$(package)/site.exp .
- install -d debian/tmp/usr/doc/$(package)/examples
+# install -d debian/tmp/usr/doc/$(package)/examples
-cd example; $(MAKE) -i distclean
- (cd example; tar cf - . ) | \
- (cd debian/tmp/usr/doc/$(package)/examples; tar xf -)
- install install.sh debian/tmp/usr/doc/$(package)/examples
+# (cd example; tar cf - . ) | \
+# (cd debian/tmp/usr/doc/$(package)/examples; tar xf -)
+# install debian/tmp/usr/doc/$(package)/examples
dpkg-gencontrol
# chown -R root.root debian/tmp
# chmod -R g-ws debian/tmp
endef
# Below here is fairly generic really
-binary: binary-indep binary-arch
+binary: binary-indep
source diff:
@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false
# AUTOMAKE_OPTIONS =
DOCBOOK = @DOCBOOK@
-TARGETS = overview.html overview.rtf # overview.dvi overview.ps
+TARGETS = overview.html overview.rtf overview.ps # overview.pdf overview.dvi
docs: $(TARGETS)
html rtf overview.pdf overview.ps overview.dvi overview.rtf overview.html: overview.sgml ref.sgml user.sgml
-clean:
- rm -f $(TARGETS)
+clean realclean distclean:
+ rm -fr $(TARGETS) DBHTOHTML* overview.junk overview.{aux,dvi,log}
install-doc: $(TARGETS)
- $(mkinstalldirs) $(DESTDIR)$(pkgdatadir)/html
+ $(mkinstalldirs) $(DESTDIR)$(pkgdatadir)/html $(DESTDIR)$(pkgdatadir)/html/stylesheet-images
$(INSTALL_DATA) overview/*.html $(DESTDIR)$(pkgdatadir)/html
-# $(INSTALL_DATA) overview.ps $(DESTDIR)$(pkgdatadir)/dejagnu.ps
+ $(INSTALL_DATA) overview/stylesheet-images/*.png $(DESTDIR)$(pkgdatadir)/html/stylesheet-images
+ $(INSTALL_DATA) overview.rtf $(DESTDIR)$(pkgdatadir)/dejagnu.ps
+ $(INSTALL_DATA) overview.ps $(DESTDIR)$(pkgdatadir)/dejagnu.ps
# $(INSTALL_DATA) overview.pdf $(DESTDIR)$(pkgdatadir)/dejagnu.pdf
+
tclsh = @tclsh@
DOCBOOK = @DOCBOOK@
-TARGETS = overview.html overview.rtf # overview.dvi overview.ps
+TARGETS = overview.html overview.rtf overview.ps # overview.pdf overview.dvi
mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
CONFIG_CLEAN_FILES =
DIST_COMMON = README Makefile.am Makefile.in configure configure.in
html rtf overview.pdf overview.ps overview.dvi overview.rtf overview.html: overview.sgml ref.sgml user.sgml
-clean:
- rm -f $(TARGETS)
+clean realclean distclean:
+ rm -fr $(TARGETS) DBHTOHTML* overview.junk overview.{aux,dvi,log}
install-doc: $(TARGETS)
- $(mkinstalldirs) $(DESTDIR)$(pkgdatadir)/html
+ $(mkinstalldirs) $(DESTDIR)$(pkgdatadir)/html $(DESTDIR)$(pkgdatadir)/html/stylesheet-images
$(INSTALL_DATA) overview/*.html $(DESTDIR)$(pkgdatadir)/html
-# $(INSTALL_DATA) overview.ps $(DESTDIR)$(pkgdatadir)/dejagnu.ps
+ $(INSTALL_DATA) overview/stylesheet-images/*.png $(DESTDIR)$(pkgdatadir)/html/stylesheet-images
+ $(INSTALL_DATA) overview.rtf $(DESTDIR)$(pkgdatadir)/dejagnu.ps
+ $(INSTALL_DATA) overview.ps $(DESTDIR)$(pkgdatadir)/dejagnu.ps
# $(INSTALL_DATA) overview.pdf $(DESTDIR)$(pkgdatadir)/dejagnu.pdf
# Tell versions [3.59,3.63) of GNU make to not export all variables.
-<!DOCTYPE book PUBLIC "-//Davenport//DTD DocBook V3.0//EN" [
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
<!-- Begin Document Specific Declarations -->
<!ENTITY dj "DejaGnu">
<!ENTITY dejagnu-copyright "
- <YEAR>2000</YEAR>
+ <YEAR>2001</YEAR>
<HOLDER>Free Software Foundation, Inc.</HOLDER>">
<!ENTITY dejagnu-code-copyright "
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
This file documents the GNU Testing Framework ``DejaGnu''
-Copyright (C) 92, 93, 94, 95, 96, 97, 98, 99, 2000 Free Software
+Copyright (C) 92, 93, 94, 95, 96, 97, 98, 99, 2000, 2001 Free Software
Foundation, Inc.
This text may be freely distributed under the terms of the GNU
">
<!ENTITY dejagnu-copyright "
-Copyright 92, 93, 94, 95, 96, 97, 98, 99, 2000 Free Software
+Copyright 92, 93, 94, 95, 96, 97, 98, 99, 2000, 2001 Free Software
Foundation, Inc.
Permission is granted to make and distribute verbatim copies of
<!entity user SYSTEM "user.sgml">
<!-- End Document Specific Declarations -->
+
]>
<book>
<bookinfo>
<title>&dj;</title>
<subtitle>The GNU Testing Framework</subtitle>
- <date>2000 Jan 24</date>
+ <date>2001 Feb 16</date>
<edition> &version</edition>
<releaseinfo> for circulation within Cygnus</releaseinfo>
<authorgroup>
<!-- </legalnotice> -->
<revhistory>
<revision>
+ <revnumber>0.6</revnumber>
+ <date>2001-2-16</date>
+ <authorinitials>rob@welcomehome.org</authorinitials>
+ <revremark>Updated for new release.</revremark>
+ </revision>
+ <revision>
<revnumber>0.5</revnumber>
<date>2000-1-24</date>
<authorinitials>rob@welcomehome.org</authorinitials>
<title>NT Support</title>
<para>To use DejaGnu on NT, you need to first install the
- <ulink URL="http://sources.redhat.com">Cygwin</ulink>
+ <ulink URL="http://sources.redhat.com/cygwin">Cygwin</ulink>
release. This works as of the B20.1 release. Cygwin is a POSIX
system for NT. This covers both utility programs, and a libray
that adds POSIX system calls to NT. Among them is pseudo tty
support for NT that emulates the POSIX pty standard. The
latest Cygwin is always available from <ulink
- URL="http://sources.redhat.com">this location</ulink>. This
+ URL="http://sources.redhat.com/cygwin">this location</ulink>. This
works well enough to run <emphasis>"make check"</emphasis> of
the GNU development tree on NT after a native build. But the
nature of pty's on NT is still evolving. Your mileage may
<title>Design Goals</title>
<para>DejaGnu grew out of the internal needs of Cygnus Solutions. (then
- Cygnus Support). Cygnus maintains and enhances a variety of free programs
- in many different environments, and we needed a testing tool that:</para>
+ Cygnus Support). Cygnus maintained and enhanced a variety of free
+ programs in many different environments, and we needed a testing
+ tool that:</para>
<itemizedlist mark="bullet">
- <listitem><para>is useful to developers while fixing
+ <listitem><para>was useful to developers while fixing
bugs.</para></listitem>
- <listitem><para>automates running many tests during a software
+ <listitem><para>automated running many tests during a software
release process.</para></listitem>
- <listitem><para>is portable among a variety of host
+ <listitem><para>was portable among a variety of host
computers.</para></listitem>
- <listitem><para>supports cross-development
+ <listitem><para>supported cross-development
testing.</para></listitem>
- <listitem><para>permits testing interactive programs, like
+ <listitem><para>permited testing interactive programs, like
<command>GDB</command>; and </para></listitem>
- <listitem><para>permits testing batch oriented programs, like
+ <listitem><para>permited testing batch oriented programs, like
<command>GCC</command>.</para></listitem>
</itemizedlist>
&ref;
</book>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:1
+sgml-indent-data:nil
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
>Adding A New Board</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
you can include one board file into another, The two main procedures used
to do this are <TT
CLASS="FUNCTION"
-><B
->load_generic_config</B
-></TT
+>load_generic_config</TT
> and
<TT
CLASS="FUNCTION"
-><B
->load_base_board_description</B
-></TT
+>load_base_board_description</TT
>. The generic config file
contains other procedures used for a certain class of target. The
board description file is where the board specfic settings go. Commonly
>Adding A Test Case To A Test Suite.</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>Adding A New Target</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>When you code an initialization module, be generous in printing
information controlled by the <TT
CLASS="FUNCTION"
-><B
->verbose</B
-></TT
+>verbose</TT
>
procedure.</P
><P
>Adding A New Tool</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>Board Config File</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>An example board config file for a GNU simulator is as
follows. <TT
CLASS="FUNCTION"
-><B
->set_board_info</B
-></TT
+>set_board_info</TT
> is a procedure that sets the
field name to the specified value. The procedures in square brackets
<I
>There are five helper procedures used in this example. The first
one, <TT
CLASS="FUNCTION"
-><B
->find gcc</B
-></TT
+>find gcc</TT
> looks for a copy of the GNU compiler in
your build tree, or it uses the one in your path. This will also return
the proper transformed name for a cross compiler if you whole build tree
is configured for one. The next helper procedures are
<TT
CLASS="FUNCTION"
-><B
->libgloss_include_flags</B
-></TT
+>libgloss_include_flags</TT
> &
<TT
CLASS="FUNCTION"
-><B
->libgloss_link_flags</B
-></TT
+>libgloss_link_flags</TT
>. These return the proper flags to
compiler and link an executable image using <A
HREF="builtins.html#LIBGLOSS"
>, the GNU BSP (Board Support Package). The final
procedures are <TT
CLASS="FUNCTION"
-><B
->newlib_include_flag</B
-></TT
+>newlib_include_flag</TT
> &
<TT
CLASS="FUNCTION"
-><B
->newlib_include_flag</B
-></TT
+>newlib_include_flag</TT
>. These find the Newlib C
library, which is a reentrant standard C library for embedded systems
comprising of non GPL'd code.</P
>Board Config File Values</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
> These are
all set by using the <TT
CLASS="FUNCTION"
-><B
->set_board_info</B
-></TT
+>set_board_info</TT
> procedure. The
parameters are the field name, followed by the value to set the field
to.</P
>DejaGnu</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="NEXT"
TITLE="Abstract"
HREF="preface.html"></HEAD
></DIV
><P
CLASS="COPYRIGHT"
->Copyright © 2000 by <SPAN
+>Copyright © 2001 by <SPAN
CLASS="HOLDER"
>Free Software Foundation, Inc.</SPAN
></P
><DL
><DT
><A
-HREF="reference.html#INSTALLATION"
+HREF="reference.html#OBTAINING"
+>Obtaining DejaGnu</A
+></DT
+><DT
+><A
+HREF="installation.html"
>Installation</A
></DT
><DD
><DL
><DT
><A
-HREF="reference.html#CONFIGURING"
+HREF="installation.html#CONFIGURING"
>Configuring DejaGnu</A
></DT
><DT
><A
-HREF="reference.html#INSTALLING"
+HREF="installation.html#INSTALLING"
>Installing DejaGnu</A
></DT
></DL
>Builtin Procedures</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
TITLE="Reference"
HREF="reference.html"><LINK
REL="PREVIOUS"
-TITLE="Reference"
-HREF="reference.html"><LINK
+TITLE="Installation"
+HREF="installation.html"><LINK
REL="NEXT"
TITLE="File Map"
HREF="filemap.html"></HEAD
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
ALIGN="left"
VALIGN="bottom"
><A
-HREF="reference.html"
+HREF="installation.html"
>Prev</A
></TD
><TD
><P
>Once you use <TT
CLASS="FUNCTION"
-><B
->setup_xfail</B
-></TT
+>setup_xfail</TT
>, the
<TT
CLASS="FUNCTION"
-><B
->fail</B
-></TT
+>fail</TT
> and <TT
CLASS="FUNCTION"
-><B
->pass</B
-></TT
+>pass</TT
> procedures
produce the messages <I
CLASS="EMPHASIS"
>Warning you must clear the expected failure after
using setup_xfail in a test case. Any call to <TT
CLASS="FUNCTION"
-><B
>pass
- </B
-></TT
+ </TT
>or <TT
CLASS="FUNCTION"
-><B
->fail</B
-></TT
+>fail</TT
>l clears the expected failure
implicitly; if the test has some other outcome, e.g. an error, you
can call <TT
CLASS="FUNCTION"
-><B
->clear_xfail</B
-></TT
+>clear_xfail</TT
> to clear the expected
failure explicitly. Otherwise, the expected-failure declaration
applies to whatever test runs next, leading to surprising
><P
>Declares a test to have passed. <TT
CLASS="FUNCTION"
-><B
->pass</B
-></TT
+>pass</TT
>
writes in the log files a message beginning with
<I
><P
>Declares a test to have failed. <TT
CLASS="FUNCTION"
-><B
->fail</B
-></TT
+>fail</TT
>
writes in the log files a message beginning with
<I
>Declares a test to have unexpectably passed, when it was
expected to be a failure. <TT
CLASS="FUNCTION"
-><B
->xpass</B
-></TT
+>xpass</TT
>
writes in the log files a message beginning with
<I
>Declares a test to have expectably
failed. <TT
CLASS="FUNCTION"
-><B
->xfail</B
-></TT
+>xfail</TT
>
writes in the log files a message beginning with
<I
> disables it: calls to
<TT
CLASS="FUNCTION"
-><B
->warning</B
-></TT
+>warning</TT
> will not turn a
<I
CLASS="EMPHASIS"
>. The default value is 3. This
value controls how many <TT
CLASS="FUNCTION"
-><B
->warning</B
-></TT
+>warning</TT
> procedures can
be called before becoming <I
CLASS="EMPHASIS"
>Declares detection of a minor error in the test case
itself. <TT
CLASS="FUNCTION"
-><B
->warning</B
-></TT
+>warning</TT
> writes in the log files a message
beginning with <I
CLASS="EMPHASIS"
></TT
>. Use <TT
CLASS="FUNCTION"
-><B
->warning</B
-></TT
+>warning</TT
> rather
than <TT
CLASS="FUNCTION"
-><B
->perror</B
-></TT
+>perror</TT
> for cases (such as communication
failure to be followed by a retry) where the test case can recover from
the error. If the optional <TT
calls to warning in a single test case also changes the effect of the
next <TT
CLASS="FUNCTION"
-><B
->pass</B
-></TT
+>pass</TT
> or <TT
CLASS="FUNCTION"
-><B
->fail</B
-></TT
+>fail</TT
> command:
the test outcome becomes <I
CLASS="EMPHASIS"
is only used to fake out the counter when using the
<TT
CLASS="FUNCTION"
-><B
->xfail</B
-></TT
+>xfail</TT
> procedure to control when it flips the
output over to <I
CLASS="EMPHASIS"
>Declares a severe error in the testing framework
itself. <TT
CLASS="FUNCTION"
-><B
->perror</B
-></TT
+>perror</TT
> writes in the log files a message
beginning with <I
CLASS="EMPHASIS"
>As a side effect, perror also changes the effect of the next
<TT
CLASS="FUNCTION"
-><B
->pass</B
-></TT
+>pass</TT
> or <TT
CLASS="FUNCTION"
-><B
->fail</B
-></TT
+>fail</TT
> command: the
test outcome becomes <I
CLASS="EMPHASIS"
is only used to fake out the counter when using the
<TT
CLASS="FUNCTION"
-><B
->xfail</B
-></TT
+>xfail</TT
> procedure to control when it flips the
output over to <I
CLASS="EMPHASIS"
>Appends an informational message to the log
file. <TT
CLASS="FUNCTION"
-><B
->note</B
-></TT
+>note</TT
> writes in the log files a message
beginning with <I
CLASS="EMPHASIS"
></TT
>. Use <TT
CLASS="FUNCTION"
-><B
->note</B
-></TT
+>note</TT
>
sparingly. The <TT
CLASS="FUNCTION"
-><B
->verbose</B
-></TT
+>verbose</TT
> should be used for most
such messages, but in cases where a message is needed in the log file
regardless of the verbosity level use <TT
CLASS="FUNCTION"
-><B
->note</B
-></TT
+>note</TT
>.</P
><DIV
CLASS="FUNCSYNOPSIS"
><P
>Declares a test was not run. <TT
CLASS="FUNCTION"
-><B
->untested</B
-></TT
+>untested</TT
> writes
in the log file a message beginning with <I
CLASS="EMPHASIS"
>Declares a test to have an unresolved
outcome. <TT
CLASS="FUNCTION"
-><B
->unresolved</B
-></TT
+>unresolved</TT
> writes in the log file a
message beginning with <I
CLASS="EMPHASIS"
>Declares that a test case depends on some facility that does not
exist in the testing environment. <TT
CLASS="FUNCTION"
-><B
->unsupported</B
-></TT
+>unsupported</TT
>
writes in the log file a message beginning with
<I
>This is the value returned by a call
to <TT
CLASS="FUNCTION"
-><B
->remote_open</B
-></TT
+>remote_open</TT
>. This closes the
connection to the target so resources can be used by
others. This parameter can be left off if the
>Starts a particular tool. For an interactive tool,
<TT
CLASS="FUNCTION"
-><B
->${tool}_start</B
-></TT
+>${tool}_start</TT
> starts and initializes the
tool, leaving the tool up and running for the test cases; an
example is <TT
CLASS="FUNCTION"
-><B
->gdb_start</B
-></TT
+>gdb_start</TT
>, the start function
for GDB. For a batch oriented tool,
<TT
CLASS="FUNCTION"
-><B
->${tool}_start</B
-></TT
+>${tool}_start</TT
> is optional; the recommended
convention is to let <TT
CLASS="FUNCTION"
-><B
->${tool}_start</B
-></TT
+>${tool}_start</TT
> run the
tool, leaving the output in a variable called
<TT
CLASS="FUNCTION"
-><B
->comp_output</B
-></TT
+>comp_output</TT
>. Test scripts can then analyze
<TT
CLASS="FUNCTION"
-><B
->$comp_output</B
-></TT
+>$comp_output</TT
> to determine the test results.
An example of this second kind of start function is
<TT
CLASS="FUNCTION"
-><B
->gcc_start</B
-></TT
+>gcc_start</TT
>, the start function for GCC.</P
><P
>DejaGnu itself does not call
<TT
CLASS="FUNCTION"
-><B
->${tool}_start</B
-></TT
+>${tool}_start</TT
>. The initialization
module <TT
CLASS="FUNCTION"
-><B
->${tool}_init.exp</B
-></TT
+>${tool}_init.exp</TT
> must call
<TT
CLASS="FUNCTION"
-><B
->${tool}_start</B
-></TT
+>${tool}_start</TT
> for interactive tools;
for batch-oriented tools, each individual test script calls
<TT
CLASS="FUNCTION"
-><B
->${tool}_start</B
-></TT
+>${tool}_start</TT
> (or makes other
arrangements to run the tool).</P
><DIV
this conditions the tool for a particular test case; for
example, <TT
CLASS="FUNCTION"
-><B
->gdb_load</B
-></TT
+>gdb_load</TT
> loads a new
executable file into the debugger. For batch oriented tools,
<TT
CLASS="FUNCTION"
-><B
->${tool}_load</B
-></TT
+>${tool}_load</TT
> may do nothing---though,
for example, the GCC support uses
<TT
CLASS="FUNCTION"
-><B
->gcc_load</B
-></TT
+>gcc_load</TT
> to load and run a binary on
the target environment. Conventionally,
<TT
CLASS="FUNCTION"
-><B
->${tool}_load</B
-></TT
+>${tool}_load</TT
> leaves the output of any
program it runs in a variable called
<SPAN
>. Writing
<TT
CLASS="FUNCTION"
-><B
->${tool}_load</B
-></TT
+>${tool}_load</TT
> can be the most complex
part of extending DejaGnu to a new tool or a new target, if
it requires much communication coding or file
downloading. Test scripts call
<TT
CLASS="FUNCTION"
-><B
->${tool}_load</B
-></TT
+>${tool}_load</TT
>.</P
><DIV
CLASS="FUNCSYNOPSIS"
interactive tools, this usually ends the interactive
session. You can also use <TT
CLASS="FUNCTION"
-><B
->${tool}_exit</B
-></TT
+>${tool}_exit</TT
>
to remove any temporary files left over from the
tests. <B
> calls
<TT
CLASS="FUNCTION"
-><B
->${tool}_exit</B
-></TT
+>${tool}_exit</TT
>.</P
><DIV
CLASS="FUNCSYNOPSIS"
>,
<TT
CLASS="FUNCTION"
-><B
->Getdirs</B
-></TT
+>Getdirs</TT
> assumes a default pattern of
<I
CLASS="EMPHASIS"
ALIGN="left"
VALIGN="top"
><A
-HREF="reference.html"
+HREF="installation.html"
>Prev</A
></TD
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Reference</TD
+>Installation</TD
><TD
WIDTH="34%"
ALIGN="center"
>Config File Values</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>The canonical configuration string for the build
host.</TD
></TR
+><TR
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>--mail</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>address</TD
+><TD
+ALIGN="LEFT"
+VALIGN="TOP"
+>Email the output log to the specified address.</TD
+></TR
></TABLE
></DIV
>
>Customizing DejaGnu</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>Debugging A Test Case</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>Design Goals</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
></H1
><P
>DejaGnu grew out of the internal needs of Cygnus Solutions. (then
- Cygnus Support). Cygnus maintains and enhances a variety of free programs
- in many different environments, and we needed a testing tool that:</P
+ Cygnus Support). Cygnus maintained and enhanced a variety of free
+ programs in many different environments, and we needed a testing
+ tool that:</P
><P
></P
><UL
><LI
STYLE="list-style-type: disc"
><P
->is useful to developers while fixing
+>was useful to developers while fixing
bugs.</P
></LI
><LI
STYLE="list-style-type: disc"
><P
->automates running many tests during a software
+>automated running many tests during a software
release process.</P
></LI
><LI
STYLE="list-style-type: disc"
><P
->is portable among a variety of host
+>was portable among a variety of host
computers.</P
></LI
><LI
STYLE="list-style-type: disc"
><P
->supports cross-development
+>supported cross-development
testing.</P
></LI
><LI
STYLE="list-style-type: disc"
><P
->permits testing interactive programs, like
+>permited testing interactive programs, like
<B
CLASS="COMMAND"
>GDB</B
><LI
STYLE="list-style-type: disc"
><P
->permits testing batch oriented programs, like
+>permited testing batch oriented programs, like
<B
CLASS="COMMAND"
>GCC</B
>Extending DejaGnu</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>File Map</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>Global Config File</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>Hints On Writing A Test Case</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
--- /dev/null
+<HTML
+><HEAD
+><TITLE
+>Installation</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
+REL="HOME"
+TITLE="DejaGnu"
+HREF="book1.html"><LINK
+REL="UP"
+TITLE="Reference"
+HREF="reference.html"><LINK
+REL="PREVIOUS"
+TITLE="Reference"
+HREF="reference.html"><LINK
+REL="NEXT"
+TITLE="Builtin Procedures"
+HREF="builtins.html"></HEAD
+><BODY
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>DejaGnu: The GNU Testing Framework</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="reference.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 5. Reference</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="builtins.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="INSTALLATION"
+>Installation</A
+></H1
+><P
+>Once you have the DejaGnu source unpacked and available, you must
+ first configure the software to specify where it is to run (and the
+ associated defaults); then you can proceed to installing it.</P
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="CONFIGURING"
+>Configuring DejaGnu</A
+></H2
+><P
+>It is usually best to configure in a directory separate from the
+ source tree, specifying where to find the source with the optional
+ <I
+CLASS="EMPHASIS"
+>--srcdir</I
+> option to
+ <I
+CLASS="EMPHASIS"
+>configure</I
+>. DejaGnu uses the GNU
+ <I
+CLASS="EMPHASIS"
+>autoconf</I
+> to configure itself. For more info on using
+ autoconf, read the GNU autoconf manual. To configure, execute the
+ <TT
+CLASS="FILENAME"
+>configure</TT
+> program, no other options are
+ required. For an example, to configure in a seperate tree for objects,
+ execute the configure script from the source tree like this:</P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> ../dejagnu-1.4/configure
+ </PRE
+></TD
+></TR
+></TABLE
+><P
+>DejaGnu doesn't care at config time if it's for testing a native
+ system or a cross system. That is determined at runtime by using the
+ config files.</P
+><P
+>You may also want to use the <B
+CLASS="COMMAND"
+>configure</B
+> option
+ <I
+CLASS="EMPHASIS"
+>--prefix</I
+> to specify where you want DejaGnu and its
+ supporting code installed. By default, installation is in subdirectories
+ of <TT
+CLASS="FILENAME"
+>/usr/local</TT
+>, but you can select any alternate
+ directory <SPAN
+CLASS="SYMBOL"
+>altdir</SPAN
+> by including
+ <TT
+CLASS="OPTION"
+>--prefix</TT
+>{altdir}} on the
+ <B
+CLASS="COMMAND"
+>configure</B
+> command line. (This value is captured in
+ the Makefile variables <I
+CLASS="EMPHASIS"
+>prefix</I
+> and
+ <I
+CLASS="EMPHASIS"
+>exec</I
+>prefix}.)</P
+><P
+>Save for a small number of example tests, the DejaGnu distribution
+ itself does not include any test suites; these are available
+ separately. Test suites for the GNU development tools are included in
+ those releases. After configuring the top-level DejaGnu directory, unpack
+ and configure the test directories for the tools you want to test; then,
+ in each test directory, run <I
+CLASS="EMPHASIS"
+>make check</I
+> to build
+ auxiliary programs required by some of the tests, and run the test
+ suites.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="INSTALLING"
+>Installing DejaGnu</A
+></H2
+><P
+>To install DejaGnu in your filesystem (either in
+ <TT
+CLASS="FILENAME"
+>/usr/local</TT
+>, or as specified by your
+ <I
+CLASS="EMPHASIS"
+>--prefix</I
+> option to <I
+CLASS="EMPHASIS"
+>configure</I
+>),
+ execute.</P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+> eg$ make install
+ </PRE
+></TD
+></TR
+></TABLE
+><P
+><I
+CLASS="EMPHASIS"
+>make install</I
+>does thes things for
+ DejaGnu:</P
+><P
+></P
+><UL
+><LI
+STYLE="list-style-type: disc"
+><P
+>Look in the path specified for executables
+ <SPAN
+CLASS="SYMBOL"
+>$exec_prefix</SPAN
+>) for directories called
+ <TT
+CLASS="FILENAME"
+>lib</TT
+> and <TT
+CLASS="FILENAME"
+>bin</TT
+>. If these
+ directories do not exist, <I
+CLASS="EMPHASIS"
+>make install</I
+> creates
+ them.</P
+></LI
+><LI
+STYLE="list-style-type: disc"
+><P
+>Create another directory in the
+ <TT
+CLASS="FILENAME"
+>share</TT
+> directory, called
+ <TT
+CLASS="FILENAME"
+>dejagnu</TT
+>, and copy all the library files into
+ it.</P
+></LI
+><LI
+STYLE="list-style-type: disc"
+><P
+>Create a directory in the
+ <TT
+CLASS="FILENAME"
+>dejagnu/share</TT
+> directory, called
+ <TT
+CLASS="FILENAME"
+>config</TT
+>, and copy all the configuration files into
+ it.</P
+></LI
+><LI
+STYLE="list-style-type: disc"
+><P
+>Copy the <I
+CLASS="EMPHASIS"
+>runtest</I
+> shell script into
+ <TT
+CLASS="FILENAME"
+>$exec_prefix/bin</TT
+>.</P
+></LI
+><LI
+STYLE="list-style-type: disc"
+><P
+>Copy <TT
+CLASS="FILENAME"
+>runtest.exp</TT
+> into
+ <TT
+CLASS="FILENAME"
+>$exec_prefix/lib/dejagnu</TT
+>. This is the main Tcl
+ code implementing DejaGnu.</P
+></LI
+></UL
+></DIV
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="reference.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="book1.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="builtins.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Reference</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="reference.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Builtin Procedures</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
\ No newline at end of file
>What's New In This Release</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
><P
>To use DejaGnu on NT, you need to first install the
<A
-HREF="http://sources.redhat.com"
+HREF="http://sources.redhat.com/cygwin"
TARGET="_top"
>Cygwin</A
>
that adds POSIX system calls to NT. Among them is pseudo tty
support for NT that emulates the POSIX pty standard. The
latest Cygwin is always available from <A
-HREF="http://sources.redhat.com"
+HREF="http://sources.redhat.com/cygwin"
TARGET="_top"
>this location</A
>. This
></DIV
></BODY
></HTML
->
+>
\ No newline at end of file
>The files DejaGnu produces.</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>Overview</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>A POSIX conforming test framework</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>Abstract</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>Reference</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
TITLE="Special variables used by test cases."
HREF="tvariables.html"><LINK
REL="NEXT"
-TITLE="Builtin Procedures"
-HREF="builtins.html"></HEAD
+TITLE="Installation"
+HREF="installation.html"></HEAD
><BODY
><DIV
CLASS="NAVHEADER"
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
ALIGN="right"
VALIGN="bottom"
><A
-HREF="builtins.html"
+HREF="installation.html"
>Next</A
></TD
></TR
></DT
><DT
><A
-HREF="reference.html#INSTALLATION"
+HREF="reference.html#OBTAINING"
+>Obtaining DejaGnu</A
+></DT
+><DT
+><A
+HREF="installation.html"
>Installation</A
></DT
><DT
><H1
CLASS="SECT1"
><A
-NAME="INSTALLATION"
->Installation</A
+NAME="OBTAINING"
+>Obtaining DejaGnu</A
></H1
><P
->Once you have the DejaGnu source unpacked and available, you must
- first configure the software to specify where it is to run (and the
- associated defaults); then you can proceed to installing it.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="CONFIGURING"
->Configuring DejaGnu</A
-></H2
-><P
->It is usually best to configure in a directory separate from the
- source tree, specifying where to find the source with the optional
- <I
-CLASS="EMPHASIS"
->--srcdir</I
-> option to
- <I
-CLASS="EMPHASIS"
->configure</I
->. DejaGnu uses the GNU
- <I
-CLASS="EMPHASIS"
->autoconf</I
-> to configure itself. For more info on using
- autoconf, read the GNU autoconf manual. To configure, execute the
- <TT
-CLASS="FILENAME"
->configure</TT
-> program, no other options are
- required. For an example, to configure in a seperate tree for objects,
- execute the configure script from the source tree like this:</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> ../dejagnu-1.4/configure
- </PRE
-></TD
-></TR
-></TABLE
-><P
->DejaGnu doesn't care at config time if it's for testing a native
- system or a cross system. That is determined at runtime by using the
- config files.</P
-><P
->You may also want to use the <B
-CLASS="COMMAND"
->configure</B
-> option
- <I
-CLASS="EMPHASIS"
->--prefix</I
-> to specify where you want DejaGnu and its
- supporting code installed. By default, installation is in subdirectories
- of <TT
-CLASS="FILENAME"
->/usr/local</TT
->, but you can select any alternate
- directory <SPAN
-CLASS="SYMBOL"
->altdir</SPAN
-> by including
- <TT
-CLASS="OPTION"
->--prefix</TT
->{altdir}} on the
- <B
-CLASS="COMMAND"
->configure</B
-> command line. (This value is captured in
- the Makefile variables <I
-CLASS="EMPHASIS"
->prefix</I
-> and
- <I
-CLASS="EMPHASIS"
->exec</I
->prefix}.)</P
-><P
->Save for a small number of example tests, the DejaGnu distribution
- itself does not include any test suites; these are available
- separately. Test suites for the GNU development tools are included in
- those releases. After configuring the top-level DejaGnu directory, unpack
- and configure the test directories for the tools you want to test; then,
- in each test directory, run <I
-CLASS="EMPHASIS"
->make check</I
-> to build
- auxiliary programs required by some of the tests, and run the test
- suites.</P
-></DIV
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="INSTALLING"
->Installing DejaGnu</A
-></H2
-><P
->To install DejaGnu in your filesystem (either in
- <TT
-CLASS="FILENAME"
->/usr/local</TT
->, or as specified by your
- <I
-CLASS="EMPHASIS"
->--prefix</I
-> option to <I
-CLASS="EMPHASIS"
->configure</I
->),
- execute.</P
-><TABLE
-BORDER="0"
-BGCOLOR="#E0E0E0"
-WIDTH="100%"
-><TR
-><TD
-><PRE
-CLASS="SCREEN"
-> eg$ make install
- </PRE
-></TD
-></TR
-></TABLE
-><P
-><I
-CLASS="EMPHASIS"
->make install</I
->does thes things for
- DejaGnu:</P
-><P
+>You can obtain DejaGnu from the DejaGnu web site at the
+ <A
+HREF="http://www.gnu.org"
+TARGET="_top"
+>Free Software Foundation</A
+>,
+ which is at <A
+HREF="http://www.gnu.org/software/dejagnu/"
+TARGET="_top"
+>www.gnu.org/software/dejagnu/
+ </A
></P
-><UL
-><LI
-STYLE="list-style-type: disc"
-><P
->Look in the path specified for executables
- <SPAN
-CLASS="SYMBOL"
->$exec_prefix</SPAN
->) for directories called
- <TT
-CLASS="FILENAME"
->lib</TT
-> and <TT
-CLASS="FILENAME"
->bin</TT
->. If these
- directories do not exist, <I
-CLASS="EMPHASIS"
->make install</I
-> creates
- them.</P
-></LI
-><LI
-STYLE="list-style-type: disc"
-><P
->Create another directory in the
- <TT
-CLASS="FILENAME"
->share</TT
-> directory, called
- <TT
-CLASS="FILENAME"
->dejagnu</TT
->, and copy all the library files into
- it.</P
-></LI
-><LI
-STYLE="list-style-type: disc"
-><P
->Create a directory in the
- <TT
-CLASS="FILENAME"
->dejagnu/share</TT
-> directory, called
- <TT
-CLASS="FILENAME"
->config</TT
->, and copy all the configuration files into
- it.</P
-></LI
-><LI
-STYLE="list-style-type: disc"
-><P
->Copy the <I
-CLASS="EMPHASIS"
->runtest</I
-> shell script into
- <TT
-CLASS="FILENAME"
->$exec_prefix/bin</TT
->.</P
-></LI
-><LI
-STYLE="list-style-type: disc"
-><P
->Copy <TT
-CLASS="FILENAME"
->runtest.exp</TT
-> into
- <TT
-CLASS="FILENAME"
->$exec_prefix/lib/dejagnu</TT
->. This is the main Tcl
- code implementing DejaGnu.</P
-></LI
-></UL
-></DIV
></DIV
></DIV
><DIV
ALIGN="right"
VALIGN="top"
><A
-HREF="builtins.html"
+HREF="installation.html"
>Next</A
></TD
></TR
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Builtin Procedures</TD
+>Installation</TD
></TR
></TABLE
></DIV
>Remote Host Testing</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>Running Tests</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>Runtest</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
><P
>Start the internal Tcl debugger. The Tcl debugger
supports breakpoints, single stepping, and other common debugging
- activities. See the document "Debugger for Tcl Applications} by Don
+ activities. See the document "Debugger for Tcl Applications" by Don
Libes. (Distributed in PostScript form with
<I
CLASS="EMPHASIS"
>Special variables used by test cases.</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
>This is the output from a
<TT
CLASS="FUNCTION"
-><B
->${tool}_load</B
-></TT
+>${tool}_load</TT
> command. This only applies to
tools like GCC and GAS which produce an object file that must in
turn be executed to complete a test.</P
>This is the output from a
<TT
CLASS="FUNCTION"
-><B
->${tool}_start</B
-></TT
+>${tool}_start</TT
> command. This is conventionally
used for batch oriented programs, like GCC and GAS, that may
produce interesting output (warnings, errors) without further
>Writing A Test Case</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.33"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.44"><LINK
REL="HOME"
TITLE="DejaGnu"
HREF="book1.html"><LINK
><TH
COLSPAN="3"
ALIGN="center"
->DejaGnu</TH
+>DejaGnu: The GNU Testing Framework</TH
></TR
><TR
><TD
<chapter id=reference>
<title>Reference</title>
+ <sect1 id=obtaining xreflabel="Obtaining DejaGnu">
+ <title>Obtaining DejaGnu</title>
+
+ <para>You can obtain DejaGnu from the DejaGnu web site at the
+ <ulink URL="http://www.gnu.org">Free Software Foundation</ulink>,
+ which is at <ulink
+ URL="http://www.gnu.org/software/dejagnu/">www.gnu.org/software/dejagnu/
+ </ulink></para>
+
+ </sect1>
+
<sect1 id=installation xreflabel="Installation">
<title>Installation</title>
execute the configure script from the source tree like this:</para>
<screen>
- ../dejagnu-1.4/configure
+ ../dejagnu-&version/configure
</screen>
<para>DejaGnu doesn't care at config time if it's for testing a native
is a list of two elements. The first is the pathname of the
testsuite expect script running. The second is a copy of what was on
the right side of the <emphasis>=</emphasis> if
- <programlisting>foo.exp="..."</programlisting>" was specified, or
+ <programlisting>foo.exp="..."</programlisting>" was specified, or
an empty string if no such argument is present. This is used by tools
like compilers where each testcase is a file.</para>
</sect1>
</chapter>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:1
+sgml-indent-data:nil
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
<term><option>--D[0-1]</option></term>
<listitem><para>Start the internal Tcl debugger. The Tcl debugger
supports breakpoints, single stepping, and other common debugging
- activities. See the document "Debugger for Tcl Applications} by Don
+ activities. See the document "Debugger for Tcl Applications" by Don
Libes. (Distributed in PostScript form with
<emphasis>expect</emphasis> as the file
<filename>expect/tcl-debug.ps.</filename>. If you specify
host.</entry>
</row>
+ <row>
+ <entry>--mail</entry>
+ <entry>address</entry>
+ <entry>Email the output log to the specified address.</entry>
+ </row>
+
</tbody>
</tgroup>
</table>
usually too dependent on terminal settings.</para>
<para>Always escape punctuation, such as <emphasis>(</emphasis>
- or <emphasis>"</emphasis>, in your patterns; for example, write
+ or <emphasis>"</emphasis>, in your patterns; for example, write
<emphasis>\(</emphasis>. If you forget to escape punctuation,
you will usually see an error message like <programlisting>extra
characters after close-quote.</programlisting></para>
</chapter>
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-namecase-general:t
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:1
+sgml-indent-data:nil
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->
\ No newline at end of file
--- /dev/null
+#! /bin/sh
+# Common stub for a few missing GNU programs while installing.
+# Copyright (C) 1996, 1997 Free Software Foundation, Inc.
+# Franc,ois Pinard <pinard@iro.umontreal.ca>, 1996.
+
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2, or (at your option)
+# any later version.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
+# 02111-1307, USA.
+
+if test $# -eq 0; then
+ echo 1>&2 "Try \`$0 --help' for more information"
+ exit 1
+fi
+
+case "$1" in
+
+ -h|--h|--he|--hel|--help)
+ echo "\
+$0 [OPTION]... PROGRAM [ARGUMENT]...
+
+Handle \`PROGRAM [ARGUMENT]...' for when PROGRAM is missing, or return an
+error status if there is no known handling for PROGRAM.
+
+Options:
+ -h, --help display this help and exit
+ -v, --version output version information and exit
+
+Supported PROGRAM values:
+ aclocal touch file \`aclocal.m4'
+ autoconf touch file \`configure'
+ autoheader touch file \`config.h.in'
+ automake touch all \`Makefile.in' files
+ bison create \`y.tab.[ch]', if possible, from existing .[ch]
+ flex create \`lex.yy.c', if possible, from existing .c
+ lex create \`lex.yy.c', if possible, from existing .c
+ makeinfo touch the output file
+ yacc create \`y.tab.[ch]', if possible, from existing .[ch]"
+ ;;
+
+ -v|--v|--ve|--ver|--vers|--versi|--versio|--version)
+ echo "missing - GNU libit 0.0"
+ ;;
+
+ -*)
+ echo 1>&2 "$0: Unknown \`$1' option"
+ echo 1>&2 "Try \`$0 --help' for more information"
+ exit 1
+ ;;
+
+ aclocal)
+ echo 1>&2 "\
+WARNING: \`$1' is missing on your system. You should only need it if
+ you modified \`acinclude.m4' or \`configure.in'. You might want
+ to install the \`Automake' and \`Perl' packages. Grab them from
+ any GNU archive site."
+ touch aclocal.m4
+ ;;
+
+ autoconf)
+ echo 1>&2 "\
+WARNING: \`$1' is missing on your system. You should only need it if
+ you modified \`configure.in'. You might want to install the
+ \`Autoconf' and \`GNU m4' packages. Grab them from any GNU
+ archive site."
+ touch configure
+ ;;
+
+ autoheader)
+ echo 1>&2 "\
+WARNING: \`$1' is missing on your system. You should only need it if
+ you modified \`acconfig.h' or \`configure.in'. You might want
+ to install the \`Autoconf' and \`GNU m4' packages. Grab them
+ from any GNU archive site."
+ files=`sed -n 's/^[ ]*A[CM]_CONFIG_HEADER([^):]*:\([^)]*\)).*/\1/p' configure.in`
+ if test -z "$files"; then
+ files=`sed -n 's/^[ ]*A[CM]_CONFIG_HEADER(\([^):]*\)).*/\1/p' configure.in`
+ test -z "$files" || files="$files.in"
+ else
+ files=`echo "$files" | sed -e 's/:/ /g'`
+ fi
+ test -z "$files" && files="config.h.in"
+ touch $files
+ ;;
+
+ automake)
+ echo 1>&2 "\
+WARNING: \`$1' is missing on your system. You should only need it if
+ you modified \`Makefile.am', \`acinclude.m4' or \`configure.in'.
+ You might want to install the \`Automake' and \`Perl' packages.
+ Grab them from any GNU archive site."
+ find . -type f -name Makefile.am -print \
+ | sed 's/^\(.*\).am$/touch \1.in/' \
+ | sh
+ ;;
+
+ bison|yacc)
+ echo 1>&2 "\
+WARNING: \`$1' is missing on your system. You should only need it if
+ you modified a \`.y' file. You may need the \`Bison' package
+ in order for those modifications to take effect. You can get
+ \`Bison' from any GNU archive site."
+ rm -f y.tab.c y.tab.h
+ if [ $# -ne 1 ]; then
+ eval LASTARG="\${$#}"
+ case "$LASTARG" in
+ *.y)
+ SRCFILE=`echo "$LASTARG" | sed 's/y$/c/'`
+ if [ -f "$SRCFILE" ]; then
+ cp "$SRCFILE" y.tab.c
+ fi
+ SRCFILE=`echo "$LASTARG" | sed 's/y$/h/'`
+ if [ -f "$SRCFILE" ]; then
+ cp "$SRCFILE" y.tab.h
+ fi
+ ;;
+ esac
+ fi
+ if [ ! -f y.tab.h ]; then
+ echo >y.tab.h
+ fi
+ if [ ! -f y.tab.c ]; then
+ echo 'main() { return 0; }' >y.tab.c
+ fi
+ ;;
+
+ lex|flex)
+ echo 1>&2 "\
+WARNING: \`$1' is missing on your system. You should only need it if
+ you modified a \`.l' file. You may need the \`Flex' package
+ in order for those modifications to take effect. You can get
+ \`Flex' from any GNU archive site."
+ rm -f lex.yy.c
+ if [ $# -ne 1 ]; then
+ eval LASTARG="\${$#}"
+ case "$LASTARG" in
+ *.l)
+ SRCFILE=`echo "$LASTARG" | sed 's/l$/c/'`
+ if [ -f "$SRCFILE" ]; then
+ cp "$SRCFILE" lex.yy.c
+ fi
+ ;;
+ esac
+ fi
+ if [ ! -f lex.yy.c ]; then
+ echo 'main() { return 0; }' >lex.yy.c
+ fi
+ ;;
+
+ makeinfo)
+ echo 1>&2 "\
+WARNING: \`$1' is missing on your system. You should only need it if
+ you modified a \`.texi' or \`.texinfo' file, or any other file
+ indirectly affecting the aspect of the manual. The spurious
+ call might also be the consequence of using a buggy \`make' (AIX,
+ DU, IRIX). You might want to install the \`Texinfo' package or
+ the \`GNU make' package. Grab either from any GNU archive site."
+ file=`echo "$*" | sed -n 's/.*-o \([^ ]*\).*/\1/p'`
+ if test -z "$file"; then
+ file=`echo "$*" | sed 's/.* \([^ ]*\) *$/\1/'`
+ file=`sed -n '/^@setfilename/ { s/.* \([^ ]*\) *$/\1/; p; q; }' $file`
+ fi
+ touch $file
+ ;;
+
+ *)
+ echo 1>&2 "\
+WARNING: \`$1' is needed, and you do not seem to have it handy on your
+ system. You might have modified some files without having the
+ proper tools for further handling them. Check the \`README' file,
+ it often tells you about the needed prerequirements for installing
+ this package. You may also peek at any GNU archive site, in case
+ some other package would contain this missing \`$1' program."
+ exit 1
+ ;;
+esac
+
+exit 0
Version: %{version}
Release: 0
Copyright: GPL
-Source: ftp://dejagnu.on.openprojects.net/pub/dejagnu/snapshots/dejagnu-1.4.tar.gz
+Source: ftp://ftp.gnu.org/gnu/dejagnu/snapshots/dejagnu-1.4.tar.gz
#Patch0: dejagnu-1.4.0-rth.patch
#Patch1: dejagnu-1.4.0-glibc21.patch
Group: Development/Tools
# Since we're building this on a debian system, we can't require these.
-#Requires: tcl >= 8.0, expect >= 5.21
+Requires: tcl >= 8.0, expect >= 5.21
BuildRoot: /tmp/%{name}-root
%description
%doc COPYING NEWS README AUTHORS INSTALL ChangeLog doc/overview
%changelog
+* Wed Feb 21 2001 Rob Savoye <rob@welcomehome.org>
+- Fixed Requires line, and changed the URL to the new ftp site.
+
* Sun Oct 31 1999 Rob Savoye <rob@welcomehome.org>
- updated to the latest snapshot
- added doc files
RUNTESTDEFAULTFLAGS = --tool runtest --srcdir $$srcdir
mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs
CONFIG_CLEAN_FILES =
-DIST_COMMON = Makefile.am Makefile.in configure.in
+DIST_COMMON = Makefile.am Makefile.in
DISTFILES = $(DIST_COMMON) $(SOURCES) $(HEADERS) $(TEXINFOS) $(EXTRA_DIST)
projects / platform / upstream / dejagnu.git / commitdiff