[NaCl SDK] Cleanup references to old newlib toolchain

native_client_sdk/doc_generated/devguide/tutorial/tutorial-part2.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="c-tutorial-getting-started-part-2">
 <span id="tutorial2"></span><h1 id="c-tutorial-getting-started-part-2"><span id="tutorial2"></span>C++ Tutorial: Getting Started (Part 2)</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#overview" id="id1">Overview</a></li>
 <li><p class="first"><a class="reference internal" href="#using-the-native-client-sdk-build-system" id="id2">Using the Native Client SDK build system</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#simplifying-the-makefile" id="id3">Simplifying the Makefile</a></li>
@@ skipping 39 matching lines @@
 <h3 id="simplifying-the-makefile">Simplifying the Makefile</h3>
 <p>The makefile from part1 only supports one toolchain (PNaCl) and one
 configuration (Release). It also only supports one source file. It&#8217;s relatively
 simple, but if we want to add support for multiple toolchains, configurations,
 source files, or build steps, it would grow increasingly complex. The SDK build
 system uses a set of variables and macros to make this possible, without
 significantly increasing the complexity of the makefile.</p>
 <p>Here is the new makefile, supporting three toolchains (PNaCl, Newlib NaCl,
 Glibc NaCl) and two configurations (Debug, Release).</p>
 <pre class="prettyprint">
-VALID_TOOLCHAINS := pnacl newlib glibc
+VALID_TOOLCHAINS := pnacl clang-newlib glibc
 
 NACL_SDK_ROOT ?= $(abspath $(CURDIR)/../..)
 include $(NACL_SDK_ROOT)/tools/common.mk
 
 TARGET = part2
 LIBS = ppapi_cpp ppapi
 
 CFLAGS = -Wall
 SOURCES = hello_tutorial.cc
 
@@ skipping 12 matching lines @@
 
 $(eval $(call NMF_RULE,$(TARGET),))
 </pre>
 <h3 id="choosing-valid-toolchains-and-including-common-mk">Choosing valid toolchains, and including common.mk</h3>
 <p>The makefile begins by specifying the toolchains that are valid for this
 project. The Native Client SDK build system supports multi-toolchain projects
 for its examples and libraries, but generally you will choose one toolchain
 when you begin your project and never change it. Please see the
 <a class="reference internal" href="/native-client/overview.html#toolchains"><em>Toolchains section of the Native Client overview</em></a> for more
 information.</p>
-<p>For this example, we support the <code>pnacl</code>, <code>newlib</code> and <code>glibc</code> toolchains.</p>
+<p>For this example, we support the <code>pnacl</code>, <code>clang-newlib</code> and <code>glibc</code>
+toolchains.</p>
 <pre class="prettyprint">
-VALID_TOOLCHAINS := pnacl newlib glibc
+VALID_TOOLCHAINS := pnacl clang-newlib glibc
 </pre>
 <p>Next, as a convenience, we specify where to find <code>NACL_SDK_ROOT</code>. Because
 this example is located in <code>pepper_$(VERSION)/getting_started/part2</code>, the
 root of the SDK is two directories up.</p>
 <pre class="prettyprint">
 NACL_SDK_ROOT ?= $(abspath $(CURDIR)/../..)
 </pre>
 <aside class="note">
 <blockquote>
 <div>In your own projects, you can use the absolute path to your installed SDK
@@ skipping 131 matching lines @@
 </pre>
 <p>This logic is now handled by <code>common.js</code>.</p>
 <h3 id="making-index-html-support-different-toolchains-and-configurations">Making index.html support different toolchains and configurations</h3>
 <p>Finally, there are a few changes to <code>index.html</code> that are not necessary for
 CSP-compliance, but help make the SDK examples more generic.</p>
 <p>First, we add some <a class="reference external" href="https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Using_data_attributes">data attributes</a>
 to the body element to specify the name, supported toolchains, supported
 configurations, and path to the <code>.nmf</code> file:</p>
 <pre class="prettyprint">
 &lt;body data-name=&quot;part2&quot;
-    data-tools=&quot;newlib glibc pnacl&quot;
+    data-tools=&quot;clang-newlib glibc pnacl&quot;
     data-configs=&quot;Debug Release&quot;
     data-path=&quot;{tc}/{config}&quot;&gt;
 ...
 </pre>
 <p><code>common.js</code> will read these data attributes to allow you to load the same
 example with different toolchains by changing the URL&#8217;s <a class="reference external" href="http://en.wikipedia.org/wiki/Query_string">query string</a>. For example, you can load the
 glibc Debug version of this example by navigating to
 <code>index.html?tc=glibc&amp;config=Debug</code>.  Path URI&#8217;s such as <code>../</code>, for example
 do not work for either the data-path parameter or its corresponding query
 string.</p>
@@ skipping 175 matching lines @@
 </li>
 <li><p class="first">Re-run the application by reloading <code>http://localhost:5103/part2</code> in
 Chrome.</p>
 <p>After Chrome loads the Native Client module, you should see the message sent
 from the module.</p>
 </li>
 </ol>
 </section>
 
 {{/partials.standard_nacl_article}}