~ubuntu-branches/ubuntu/saucy/db/saucy-proposed

« back to all changes in this revision

Viewing changes to docs/programmer_reference/build_unix_test.html

  • Committer: Bazaar Package Importer
  • Author(s): Colin Watson
  • Date: 2010-11-05 15:02:09 UTC
  • mfrom: (13.1.12 sid)
  • Revision ID: james.westby@ubuntu.com-20101105150209-ppvyn0619pu014xo
Tags: 5.1.19-1ubuntu1
* Resynchronise with Debian.  Remaining changes:
  - Pass --build/--host to configure to support cross-building, and don't
    override CC.
  - Disable the Java build when cross-building, for now.

Show diffs side-by-side

added added

removed removed

Lines of Context:
1
 
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
2
 
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3
 
<html xmlns="http://www.w3.org/1999/xhtml">
4
 
  <head>
5
 
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
6
 
    <title>Running the test suite under UNIX</title>
7
 
    <link rel="stylesheet" href="gettingStarted.css" type="text/css" />
8
 
    <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" />
9
 
    <link rel="start" href="index.html" title="Berkeley DB Programmer's Reference Guide" />
10
 
    <link rel="up" href="build_unix.html" title="Chapter 27.  Building Berkeley DB for UNIX/POSIX" />
11
 
    <link rel="prev" href="build_unix_shlib.html" title="Dynamic shared libraries" />
12
 
    <link rel="next" href="build_unix_notes.html" title="Architecture independent FAQ" />
13
 
  </head>
14
 
  <body>
15
 
    <div class="navheader">
16
 
      <table width="100%" summary="Navigation header">
17
 
        <tr>
18
 
          <th colspan="3" align="center">Running the test suite under UNIX</th>
19
 
        </tr>
20
 
        <tr>
21
 
          <td width="20%" align="left"><a accesskey="p" href="build_unix_shlib.html">Prev</a> </td>
22
 
          <th width="60%" align="center">Chapter 27. 
23
 
                Building Berkeley DB for UNIX/POSIX
24
 
        </th>
25
 
          <td width="20%" align="right"> <a accesskey="n" href="build_unix_notes.html">Next</a></td>
26
 
        </tr>
27
 
      </table>
28
 
      <hr />
29
 
    </div>
30
 
    <div class="sect1" lang="en" xml:lang="en">
31
 
      <div class="titlepage">
32
 
        <div>
33
 
          <div>
34
 
            <h2 class="title" style="clear: both"><a id="build_unix_test"></a>Running the test suite under UNIX</h2>
35
 
          </div>
36
 
        </div>
37
 
      </div>
38
 
      <p>The Berkeley DB test suite is built if you specify
39
 
<a class="link" href="build_unix_conf.html#build_unix_conf.--enable-test">--enable-test</a>
40
 
as an argument when configuring Berkeley DB.  The test suite also
41
 
requires that you configure and build the Tcl interface to the
42
 
library.</p>
43
 
      <p>Before running the tests for the first time, you may need to edit the
44
 
<code class="filename">include.tcl</code> file in your build directory.  The
45
 
Berkeley DB configuration assumes that you intend to use the
46
 
version of the tclsh utility included in the Tcl installation with which
47
 
Berkeley DB was configured to run the test suite, and further
48
 
assumes that the test suite will be run with the libraries prebuilt in
49
 
the Berkeley DB build directory.  If either of these assumptions
50
 
are incorrect, you will need to edit the <code class="filename">include.tcl</code> file and
51
 
change the following line to correctly specify the full path to the
52
 
version of tclsh with which you are going to run the test suite:</p>
53
 
      <pre class="programlisting">set tclsh_path ...</pre>
54
 
      <p>You may also need to change the following line to correctly specify the
55
 
path from the directory where you are running the test suite to the
56
 
location of the Berkeley DB Tcl library you built:</p>
57
 
      <pre class="programlisting">set test_path ...</pre>
58
 
      <p>It may not be necessary that this be a full path if you have configured
59
 
your system's shared library mechanisms to search the directory where
60
 
you built or installed the Tcl library.</p>
61
 
      <p>All Berkeley DB tests are run from within <span class="bold"><strong>tclsh</strong></span>.  After
62
 
starting tclsh, you must source the file <code class="filename">test.tcl</code> in the test
63
 
directory.  For example, if you built in the <code class="filename">build_unix</code>
64
 
directory of the distribution, this would be done using the following
65
 
command:</p>
66
 
      <pre class="programlisting">% source ../test/test.tcl</pre>
67
 
      <p>If no errors occur, you should get a "%" prompt.</p>
68
 
      <p>You are now ready to run tests in the test suite; see
69
 
<a class="xref" href="test.html#test_run" title="Running the test suite">Running the test suite</a> for more
70
 
information.</p>
71
 
    </div>
72
 
    <div class="navfooter">
73
 
      <hr />
74
 
      <table width="100%" summary="Navigation footer">
75
 
        <tr>
76
 
          <td width="40%" align="left"><a accesskey="p" href="build_unix_shlib.html">Prev</a> </td>
77
 
          <td width="20%" align="center">
78
 
            <a accesskey="u" href="build_unix.html">Up</a>
79
 
          </td>
80
 
          <td width="40%" align="right"> <a accesskey="n" href="build_unix_notes.html">Next</a></td>
81
 
        </tr>
82
 
        <tr>
83
 
          <td width="40%" align="left" valign="top">Dynamic shared libraries </td>
84
 
          <td width="20%" align="center">
85
 
            <a accesskey="h" href="index.html">Home</a>
86
 
          </td>
87
 
          <td width="40%" align="right" valign="top"> Architecture independent FAQ</td>
88
 
        </tr>
89
 
      </table>
90
 
    </div>
91
 
  </body>
92
 
</html>