[NaCl SDK] Cleanup references to old newlib toolchain

native_client_sdk/doc_generated/sdk/examples.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <span class="target" id="sdk-examples-2"></span><section id="examples">
 <h1 id="examples">Examples</h1>
 <p>Every Native Client SDK bundle comes with a folder of example applications.
 Each example demonstrates one or two key Native Client programming concepts.
 After you&#8217;ve <a class="reference internal" href="/native-client/sdk/download.html"><em>downloaded the SDK</em></a>, follow the instructions
 on this page to build and run the examples.</p>
 <p>Your version of Chrome must be equal to or greater than the version of your SDK
 bundle. For example, if you&#8217;re developing with the <code>pepper_35</code> bundle, you
 must use Google Chrome version 35 or greater. To find out what version of Chrome
 you&#8217;re using, type <code>about:chrome</code> or <code>about:version</code> in the Chrome address
 bar.</p>
 <h2 id="build-the-sdk-examples"><span id="id1"></span>Build the SDK examples</h2>
 <p>The Makefile scripts for the SDK examples can build multiple versions of the
-examples using any of the three SDK toolchains (newlib, glibc, and PNaCl) and in
-both release and debug configurations. Note that some examples, <code>dlopen</code> for
-example, build only with particular toolchains.</p>
+examples using any of the three SDK toolchains (clang-newlib, glibc, and PNaCl)
+and in both release and debug configurations. Note that some examples,
+<code>dlopen</code> for example, build only with particular toolchains.</p>
 <p>Find the toolchains for each example by looking at the <code>VALID_TOOLCHAINS</code>
 variable in the Makefile for a particular example. The first item listed is the
 default. It&#8217;s built when you run an example make file without parameters. for
 example running make in the <code>core</code> directory of pepper_35 builds the example
-using the <code>newlib</code> toolchain.</p>
+using the <code>glibc</code> toolchain.</p>
 <pre class="prettyprint">
 $ cd pepper_35/examples/api/core
 $ make
-  CXX  newlib/Release/core_x86_32.o
-  LINK newlib/Release/core_unstripped_x86_32.nexe
-  VALIDATE newlib/Release/core_unstripped_x86_32.nexe
-  CXX  newlib/Release/core_x86_64.o
-  LINK newlib/Release/core_unstripped_x86_64.nexe
-  VALIDATE newlib/Release/core_unstripped_x86_64.nexe
-  CXX  newlib/Release/core_arm.o
-  LINK newlib/Release/core_unstripped_arm.nexe
-  VALIDATE newlib/Release/core_unstripped_arm.nexe
-  STRIP newlib/Release/core_x86_32.nexe
-  STRIP newlib/Release/core_x86_64.nexe
-  STRIP newlib/Release/core_arm.nexe
-  CREATE_NMF newlib/Release/core.nmf
+  CXX  glibc/Release/core_x86_32.o
+  LINK glibc/Release/core_unstripped_x86_32.nexe
+  VALIDATE glibc/Release/core_unstripped_x86_32.nexe
+  CXX  glibc/Release/core_x86_64.o
+  LINK glibc/Release/core_unstripped_x86_64.nexe
+  VALIDATE glibc/Release/core_unstripped_x86_64.nexe
+  CXX  glibc/Release/core_arm.o
+  LINK glibc/Release/core_unstripped_arm.nexe
+  VALIDATE glibc/Release/core_unstripped_arm.nexe
+  STRIP glibc/Release/core_x86_32.nexe
+  STRIP glibc/Release/core_x86_64.nexe
+  STRIP glibc/Release/core_arm.nexe
+  CREATE_NMF glibc/Release/core.nmf
 </pre>
 <p>As you can see, this produces a number of architecture specific nexe files in
 the <code>pepper_35/examples/api/core/Release</code> directory.  Create debug versions by
 using the <code>CONFIG</code> parameter of the make command.</p>
 <pre class="prettyprint">
 $make CONFIG=Debug
 </pre>
 <p>This creates similar output, but in <code>pepper_35/examples/api/core/Debug</code>.</p>
 <p>Select a different toolchain with the <code>TOOLCHAIN</code> parameter.  For example:</p>
 <pre class="prettyprint">
 $ cd pepper_35/examples/api/core
 $ make TOOLCHAIN=pnacl CONFIG=Release
   CXX  pnacl/Release/core.o
   LINK pnacl/Release/core_unstripped.bc
   FINALIZE pnacl/Release/core_unstripped.pexe
   CREATE_NMF pnacl/Release/core.nmf
 </pre>
 <p>You can also set <code>TOOLCHAIN</code> to <code>all</code> to build all Release versions with
 default toolchains.</p>
 <pre class="prettyprint">
 $ cd pepper_35/examples/api/core
 $ make TOOLCHAIN=all
-make TOOLCHAIN=newlib
+make TOOLCHAIN=clang-newlib
 make[1]: Entering directory 'pepper_35/examples/api/core'
-  CXX  newlib/Release/core_x86_32.o
-  LINK newlib/Release/core_unstripped_x86_32.nexe
-  VALIDATE newlib/Release/core_unstripped_x86_32.nexe
-  CXX  newlib/Release/core_x86_64.o
-  LINK newlib/Release/core_unstripped_x86_64.nexe
-  VALIDATE newlib/Release/core_unstripped_x86_64.nexe
-  CXX  newlib/Release/core_arm.o
-  LINK newlib/Release/core_unstripped_arm.nexe
-  VALIDATE newlib/Release/core_unstripped_arm.nexe
-  STRIP newlib/Release/core_x86_32.nexe
-  STRIP newlib/Release/core_x86_64.nexe
-  STRIP newlib/Release/core_arm.nexe
-  CREATE_NMF newlib/Release/core.nmf
+  CXX  clang-newlib/Release/core_x86_32.o
+  LINK clang-newlib/Release/core_unstripped_x86_32.nexe
+  VALIDATE clang-newlib/Release/core_unstripped_x86_32.nexe
+  CXX  clang-newlib/Release/core_x86_64.o
+  LINK clang-newlib/Release/core_unstripped_x86_64.nexe
+  VALIDATE clang-newlib/Release/core_unstripped_x86_64.nexe
+  CXX  clang-newlib/Release/core_arm.o
+  LINK clang-newlib/Release/core_unstripped_arm.nexe
+  VALIDATE clang-newlib/Release/core_unstripped_arm.nexe
+  STRIP clang-newlib/Release/core_x86_32.nexe
+  STRIP clang-newlib/Release/core_x86_64.nexe
+  STRIP clang-newlib/Release/core_arm.nexe
+  CREATE_NMF clang-newlib/Release/core.nmf
 make[1]: Leaving directory 'pepper_35/examples/api/core'
 make TOOLCHAIN=glibc
 make[1]: Entering directory 'pepper_35/examples/api/core'
   CXX  glibc/Release/core_x86_32.o
   LINK glibc/Release/core_unstripped_x86_32.nexe
   VALIDATE glibc/Release/core_unstripped_x86_32.nexe
   CXX  glibc/Release/core_x86_64.o
   LINK glibc/Release/core_unstripped_x86_64.nexe
   VALIDATE glibc/Release/core_unstripped_x86_64.nexe
   ...
   (content excerpted)
   ...
 </pre>
 <h3 id="build-results"><span id="id2"></span>Build results</h3>
 <p>After running <code>make</code>, example directories will contain one or more of the
 following subdirectories, depending on which Makefile you run:</p>
 <ul class="small-gap">
-<li><code>newlib</code> with subdirectories <code>Debug</code> and <code>Release</code>;</li>
+<li><code>clang-newlib</code> with subdirectories <code>Debug</code> and <code>Release</code>;</li>
 <li><code>glibc</code> with subdirectories <code>Debug</code> and <code>Release</code>;</li>
 <li><code>pnacl</code> with subdirectories <code>Debug</code> and <code>Release</code>;</li>
 </ul>
-<p>For the newlib and glibc toolchains the Debug and Release subdirectories
+<p>For the clang-newlib and glibc toolchains the Debug and Release subdirectories
 contain .nexe files for all target architectures. For the PNaCl toolchain
 they contain a single .pexe file. PNaCl debug also produces pre-translated
 .nexe files, for ease of debugging. All Debug and Release directories contain
 a manifest (.nmf) file that references the associated .nexe or .pexe files.
 For information about Native Client manifest files, see the <a class="reference internal" href="/native-client/overview.html"><em>Technical
 Overview</em></a>.</p>
 <p>For details on how to use <code>make</code>, see the <a class="reference external" href="http://www.gnu.org/software/make/manual/make.html">GNU &#8216;make&#8217; Manual</a>. For details on how to
 use the SDK toolchain itself, see <a class="reference internal" href="/native-client/devguide/devcycle/building.html"><em>Building Native Client Modules</em></a>.</p>
 <h2 id="run-the-sdk-examples"><span id="running-the-sdk-examples"></span>Run the SDK examples</h2>
 <h3 id="disable-the-chrome-cache"><span id="disable-chrome-cache"></span>Disable the Chrome cache</h3>
@@ skipping 91 matching lines @@
 0x000000000fa00080 in ?? ()
 </pre>
 <p>At this point, you can use the standard GDB commands to debug your NaCl module.
 The most common commands you will use to debug are <code>continue</code>, <code>step</code>,
 <code>next</code>, <code>break</code> and <code>backtrace</code>. See
 <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html"><em>Debugging</em></a> for more information about
 debugging a Native Client application.</p>
 </section>
 
 {{/partials.standard_nacl_article}}