Merged from 1.33.0 release

[SVN r30540]

historic/jam/src/index.html

@@ -367,8 +367,7 @@ sh ./build.sh
     </tr>
 
     <tr>
-      <td valign="top"><a href=
-      "http://developer.intel.com/software/products/kcc/">kcc</a>, Intel KAI
+      <td valign="top">kcc, Intel KAI
       C++</td>
 
       <td valign="top">* <tt>KCC</tt> in <tt>PATH</tt></td>

jam_src/index.html

@@ -367,8 +367,7 @@ sh ./build.sh
     </tr>
 
     <tr>
-      <td valign="top"><a href=
-      "http://developer.intel.com/software/products/kcc/">kcc</a>, Intel KAI
+      <td valign="top">kcc, Intel KAI
       C++</td>
 
       <td valign="top">* <tt>KCC</tt> in <tt>PATH</tt></td>

v1/build_system.htm

@@ -34,7 +34,7 @@
   <p>Boost.Build is a system for large project software construction built on
   <a href="../jam_src/index.html">Boost.Jam</a>, a descendant of "<a href=
   "http://www.perforce.com/jam/jam.html">Perforce Jam</a>", an open-source
-  make replacement<a href="#1">[1]</a>. Key features are:</p>
+  make replacement<a href="#one">[1]</a>. Key features are:</p>
 
   <ul>
     <li>A simple target description language</li>
@@ -497,7 +497,7 @@ subinclude foo/bar/baz <font color="#7F7F7F">foo/bar/...</font> ;
     dependency of built targets. For example, an external library might be
     specified with a dependency-feature: if the library is updated, the
     target will be updated also. The <tt>&lt;library-file&gt;</tt> feature
-    works this way <a href="#2">[2]</a>.</li>
+    works this way <a href="#two">[2]</a>.</li>
   </ol>
 
   <p>A feature-value pair is known as a <b>build property</b>, or simply
@@ -653,12 +653,12 @@ subinclude foo/bar/baz <font color="#7F7F7F">foo/bar/...</font> ;
   <p>The Jam command line ends with an optional list of target names; if no
   target names are supplied, the built-in pseudotarget <tt>all</tt> is built.
   In a large project, naming targets can be dicey because of collisions. Jam
-  uses a mechanism called <a href="#grist">grist</a> to distinguish targets
-  that would otherwise have the same name. Fortunately, you won't often have
-  to supply grist at the command-line. When you declare a main target, a Jam
-  pseudotarget of the same name is created which depends on <i>all</i> of the
-  subvariants requested for your invocation of the build system. For example,
-  if your subproject declares:</p>
+  uses a mechanism called grist to distinguish targets that would otherwise
+  have the same name. Fortunately, you won't often have to supply grist at
+  the command-line. When you declare a main target, a Jam pseudotarget of the
+  same name is created which depends on <i>all</i> of the subvariants
+  requested for your invocation of the build system. For example, if your
+  subproject declares:</p>
 
   <blockquote>
     <pre>
@@ -1538,27 +1538,23 @@ flags msvc HDRS &lt;include&gt; ;
     the source directories (they may be read-only)</li>
   </ul>
 
-  <h2><a name="footnotes" id="footnotes">Footnotes</a></h2><a name="1" id=
-  "1">[1]</a> Boost Jam is actually descended directly from <a href=
+  <h2><a name="footnotes" id="footnotes">Footnotes</a></h2><a name="one" id=
+  "one">[1]</a> Boost Jam is actually descended directly from <a href=
   "http://freetype.sourceforge.net/jam/index.html">FTJam</a>, which was
   itself a variant of <a href=
   "http://www.perforce.com/jam/jam.html">Jam/MR</a>. It is hoped that crucial
   features we rely on will eventually be incorporated back into the Jam/MR
   release.
 
-  <p><a name="2" id="2">[2]</a> Note: right now, a dependency feature of a
-  main target makes <b>all</b> resulting built targets dependent, including
+  <p><a name="two" id="two">[2]</a> Note: right now, a dependency feature of
+  a main target makes <b>all</b> resulting built targets dependent, including
   intermediate targets. That means that if an executable is dependent on an
   external library, and that library changes, all the sources comprising the
   executable will be recompiled as well. This behavior should probably be
   fixed.</p>
   <hr>
 
-  <p>Revised 
-  <!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan
-                                                  -->8 September, 2003 
-<!--webbot bot="Timestamp" endspan i-checksum="13972"
-                                                  --></p>
+  <p>Revised $Date$</p>
 
   <p>Copyright &copy; Dave Abrahams 2001.</p>
 

v1/gcc-nocygwin-tools.html

@@ -1,3 +1,5 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+
 <html>
 <head>
   <meta name="generator" content=
@@ -115,8 +117,8 @@
 
   <p>It is also possible to add support manually to older Cygwin compilers if
   you won't upgrade for some reason. See for instance <a href=
-  "http://www.nanotech.wisc.edu/~khan/software/gnu-win32/mno-cygwin-howto.txt">
-  these details</a>, or search for "mno-cygwin" and "c++" on the web or the
+  "http://www.delorie.com/howto/cygwin/mno-cygwin-howto.html">these
+  details</a>, or search for "mno-cygwin" and "c++" on the web or the
   <a href="http://cygwin.com/lists.html">Cygwin mailing lists</a>.</p>
 
   <p>Another, probably more difficult option, is to install the STLport

v1/kcc-tools.html

@@ -30,13 +30,12 @@
 
   <h2>Introduction</h2>
 
-  <p>Boost.Build's <a href=
-  "http://developer.intel.com/software/products/kcc/">kcc</a> toolset
+  <p>Boost.Build's kcc toolset
   supports the Intel KAI C++ Compiler.</p>
 
   <p><b>WARNING:</b> This compiler is no longer being distributed by Intel,
   see the <a href=
-  "http://developer.intel.com/software/products/kcc/announcement.htm">announcement</a>
+  "http://www.nersc.gov/nusers/resources/software/kai/kcc/">announcement</a>
   for details.</p>
 
   <h2>Configuration Variables</h2>The kcc toolset responds to the following

v1/mingw-tools.html

@@ -35,7 +35,7 @@
   "http://www.mingw.org">MinGW</a> configuration. This is hosted on Windows
   and targets standalone Windows objects.</p>
 
-  <h2>Configuration Variables</h2>The mingw toolset responds to the following
+  <h2><a name="configuration"></a>Configuration Variables</h2>The mingw toolset responds to the following
   variables which can be set in the environment or configured on the jam
   command-line using <code>-s<i>VARIABLE_NAME</i>=</code><i>value</i>. This
   toolset is an extension to the <a href="gcc-tools.html">gcc toolset</a>.

v1/mipspro-tools.html

@@ -32,7 +32,7 @@
   <h2>Introduction</h2>
 
   <p>Boost.Build's <a href=
-  "http://www.sgi.com/developers/devtools/languages/mipspro.html">mipspro</a>
+  "http://www.sgi.com/products/software/irix/tools/mipspro.html">mipspro</a>
   toolset supports the SGI MIPSpro C and C++ compilers.</p>
 
   <h2>Configuration Variables</h2>The mipspro toolset responds to the

v1/python.jam

@@ -428,13 +428,6 @@ rule Link-PYD
     if $(UNIX) 
     {
         LINK_LIBPATH on $(<) = [ join $(gRUN_LD_LIBRARY_PATH($(<))) : $(SPLITPATH) ] ;
-        
-        if $(OS) = AIX
-        {
-            # explicitly designate the exported init<module> function
-            LINKFLAGS on $(<) += "-e init$(<[1]:B)" ; 
-            Aix-Implib-Action $(<) : $(>) ;
-        }
     }
     gRUN_PYTHONPATH($(<)) += $(gLOCATE($(<[1]))) ;
     .do-link $(<) : $(>) : PYD ;

v1/sunpro-tools.html

@@ -42,7 +42,7 @@
 
   <p>As of this writing (November 2003) the Sun C++ compiler has difficulty
   building many of the libraries included with Boost. <a href=
-  "http://boost.sourceforge.net/regression-logs/cs-SunOS.html">Complete
+  "http://www.boost.org/regression/release/developer/summary.html">Complete
   regression test information is available</a>, although absent from the
   regression tables are some libraries that Sun C++ has particular difficulty
   with, including <code><a href=
@@ -200,9 +200,7 @@
   </table>
   <hr>
 
-  <p>Revised 
-  <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->
-   03 Nov, 2003 <!--webbot bot="Timestamp" endspan i-checksum="39359" --></p>
+  <p>Revised $Date$</p>
 
   <p>Christopher Currie, Gennadiy Rozental, Jens Maurer</p>
 </body>

v1/vacpp-tools.html

@@ -31,7 +31,7 @@
   <h2>Introduction</h2>
 
   <p>Boost.Build's <a href=
-  "http://www-3.ibm.com/software/ad/vacpp/">vacpp</a> toolset supports the
+  "http://www-306.ibm.com/software/awdtools/vacpp/">vacpp</a> toolset supports the
   IBM VisualAge C++.</p>
 
   <h2>Configuration Variables</h2>There currently are no user configurable

v1/vc-8_0-amd64-tools.jam

@@ -1,4 +1,4 @@
-extends-toolset vc-8_0-tools.jam ;
+extends-toolset vc-8_0 ;
 
 if $(VC80_ROOT)
 {