1.42.0 prep

[SVN r57970]

1 files changed, 9 insertions, 9 deletions

diff --git a/more/getting_started/unix-variants.html b/more/getting_started/unix-variants.html
index 1172cac894..47c29d8588 100644
--- a/more/getting_started/unix-variants.html
+++ b/more/getting_started/unix-variants.html
@@ -63,12 +63,12 @@
 <p>The most reliable way to get a copy of Boost is to download a
 distribution from <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&amp;package_id=8041">SourceForge</a>:</p>
 <ol class="arabic">
-<li><p class="first">Download <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&amp;package_id=8041"><tt class="docutils literal">boost_1_41_0</tt><tt class="docutils literal">.tar.bz2</tt></a>.</p>
+<li><p class="first">Download <a class="reference external" href="http://sourceforge.net/project/showfiles.php?group_id=7586&amp;package_id=8041"><tt class="docutils literal">boost_1_42_0</tt><tt class="docutils literal">.tar.bz2</tt></a>.</p>
 </li>
 <li><p class="first">In the directory where you want to put the Boost installation,
 execute</p>
 <pre class="literal-block">
-tar --bzip2 -xf <em>/path/to/</em><tt class="docutils literal">boost_1_41_0</tt>.tar.bz2
+tar --bzip2 -xf <em>/path/to/</em><tt class="docutils literal">boost_1_42_0</tt>.tar.bz2
 </pre>
 </li>
 </ol>
@@ -91,7 +91,7 @@ from <a class="reference external" href="http://sourceforge.net/project/showfile
 <h1><a class="toc-backref" href="#id22">2&nbsp;&nbsp;&nbsp;The Boost Distribution</a></h1>
 <p>This is a sketch of the resulting directory structure:</p>
 <pre class="literal-block">
-<strong>boost_1_41_0</strong><strong>/</strong> .................<em>The “boost root directory”</em>
+<strong>boost_1_42_0</strong><strong>/</strong> .................<em>The “boost root directory”</em>
    <strong>index.htm</strong> .........<em>A copy of www.boost.org starts here</em>
    <strong>boost</strong><strong>/</strong> .........................<em>All Boost Header files</em>
    <tt class="docutils literal"> </tt>
@@ -136,7 +136,7 @@ anything you can use in these directories.</p>
 </div>
 <p>It's important to note the following:</p>
 <ol class="arabic" id="boost-root-directory">
-<li><p class="first">The path to the <strong>boost root directory</strong> (often <tt class="docutils literal">/usr/local/</tt><tt class="docutils literal">boost_1_41_0</tt>) is
+<li><p class="first">The path to the <strong>boost root directory</strong> (often <tt class="docutils literal">/usr/local/</tt><tt class="docutils literal">boost_1_42_0</tt>) is
 sometimes referred to as <tt class="docutils literal">$BOOST_ROOT</tt> in documentation and
 mailing lists .</p>
 </li>
@@ -231,7 +231,7 @@ int main()
 <p>Now, in the directory where you saved <tt class="docutils literal">example.cpp</tt>, issue the
 following command:</p>
 <pre class="literal-block">
-c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_41_0</tt> example.cpp -o example
+c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_42_0</tt> example.cpp -o example
 </pre>
 <p>To test the result, type:</p>
 <pre class="literal-block">
@@ -262,7 +262,7 @@ you'll need to acquire library binaries.</p>
 <p>Issue the following commands in the shell (don't type <tt class="docutils literal">$</tt>; that
 represents the shell's prompt):</p>
 <pre class="literal-block">
-<strong>$</strong> cd <em>path/to/</em><tt class="docutils literal">boost_1_41_0</tt>
+<strong>$</strong> cd <em>path/to/</em><tt class="docutils literal">boost_1_42_0</tt>
 <strong>$</strong> ./bootstrap.sh --help
 </pre>
 <p>Select your configuration options and invoke <tt class="docutils literal">./bootstrap.sh</tt> again
@@ -434,7 +434,7 @@ bjam <strong>--build-dir=</strong><a class="reference internal" href="#id11"><em
 please see the <a class="reference external" href="http://www.boost.org/boost-build2/doc/html/bbv2/advanced/invocation.html">Boost.Build documentation</a>.</p>
 <p>For example, your session might look like this:</p>
 <pre class="literal-block">
-$ cd ~/<tt class="docutils literal">boost_1_41_0</tt>
+$ cd ~/<tt class="docutils literal">boost_1_42_0</tt>
 $ bjam <strong>--build-dir=</strong>/tmp/build-boost <strong>toolset=</strong>gcc stage
 </pre>
 <p>That will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, “<tt class="docutils literal"><span class="pre">--build-type=complete</span></tt>”.</p>
@@ -549,14 +549,14 @@ project.</li>
 <ol class="upperalpha">
 <li><p class="first">You can specify the full path to each library:</p>
 <pre class="literal-block">
-$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_41_0</tt> example.cpp -o example <strong>\</strong>
+$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_42_0</tt> example.cpp -o example <strong>\</strong>
    <strong>~/boost/stage/lib/libboost_regex-gcc34-mt-d-1_36.a</strong>
 </pre>
 </li>
 <li><p class="first">You can separately specify a directory to search (with <tt class="docutils literal"><span class="pre">-L</span></tt><em>directory</em>) and a library name to search for (with <tt class="docutils literal"><span class="pre">-l</span></tt><em>library</em>,<a class="footnote-reference" href="#lowercase-l" id="id15"><sup>2</sup></a> dropping the filename's leading <tt class="docutils literal">lib</tt> and trailing
 suffix (<tt class="docutils literal">.a</tt> in this case):</p>
 <pre class="literal-block">
-$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_41_0</tt> example.cpp -o example <strong>\</strong>
+$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_42_0</tt> example.cpp -o example <strong>\</strong>
    <strong>-L~/boost/stage/lib/ -lboost_regex-gcc34-mt-d-1_36</strong>
 </pre>
 <p>As you can see, this method is just as terse as method A for one