[NaCl SDK] Cleanup references to old newlib toolchain

native_client_sdk/doc_generated/devguide/devcycle/building.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="building">
 <span id="devcycle-building"></span><h1 id="building"><span id="devcycle-building"></span>Building</h1>
 <div class="contents local" id="table-of-contents" style="display: none">
 <p class="topic-title first">Table Of Contents</p>
 <ul class="small-gap">
 <li><p class="first"><a class="reference internal" href="#introduction" id="id4">Introduction</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#target-architectures" id="id5">Target architectures</a></li>
@@ skipping 54 matching lines @@
 <a class="reference internal" href="/native-client/overview.html#application-files"><em>manifest file</em></a> will then specify which version
 of the module to load based on the end-user&#8217;s architecture. The SDK
 includes a script for generating manifest files called <code>create_nmf.py</code>.  This
 script is located in the <code>pepper_&lt;version&gt;/tools/</code> directory, meaning under
 your installed pepper bundle. For examples of how to compile modules for
 multiple target architectures and how to generate manifest files, see the
 Makefiles included with the SDK examples.</p>
 <p>This section will mostly cover PNaCl, but also describes how to build
 <strong>nexe</strong> applications.</p>
 <h3 id="c-libraries">C libraries</h3>
-<p>The PNaCl SDK has a single choice of C library: <a class="reference external" href="http://sourceware.org/newlib/">newlib</a>.</p>
-<p>The Native Client SDK also has a GCC-based toolchain for building
-<strong>nexes</strong>. The GCC-based toolchain has support for two C libraries:
-<a class="reference external" href="http://sourceware.org/newlib/">newlib</a> and <a class="reference external" href="http://www.gnu.org/software/libc/">glibc</a>.  See <a class="reference internal" href="/native-client/devguide/devcycle/dynamic-loading.html"><em>Dynamic Linking &amp; Loading with glibc</em></a> for information about these libraries, including factors to
-help you decide which to use.</p>
+<p>The PNaCl SDK uses the <a class="reference external" href="http://sourceware.org/newlib/">newlib</a> C library.  The Native Client SDK also has a
+GCC-based toolchain for building <strong>nexes</strong> using the <a class="reference external" href="http://www.gnu.org/software/libc/">glibc</a> C library.  See
+<a class="reference internal" href="/native-client/devguide/devcycle/dynamic-loading.html"><em>Dynamic Linking &amp; Loading with glibc</em></a> for information
+about these libraries, including factors to help you decide which to use.</p>
 <h3 id="c-standard-libraries"><span id="building-cpp-libraries"></span>C++ standard libraries</h3>
 <p>The PNaCl SDK can use either LLVM&#8217;s <a class="reference external" href="http://libcxx.llvm.org/">libc++</a>
 (the current default) or GCC&#8217;s <a class="reference external" href="http://gcc.gnu.org/libstdc++">libstdc++</a> (deprecated). The
 <code>-stdlib=[libc++|libstdc++]</code> command line argument can be used to
 choose which standard library to use.</p>
-<p>The GCC-based Native Client SDK only has support for GCC&#8217;s <a class="reference external" href="http://gcc.gnu.org/libstdc++">libstdc++</a>.</p>
+<p>The GCC-based toolchain only has support for GCC&#8217;s <a class="reference external" href="http://gcc.gnu.org/libstdc++">libstdc++</a>.</p>
 <p>C++11 library support is only complete in libc++ but other non-library language
 features should work regardless of which standard library is used. The
 <code>-std=gnu++11</code> command line argument can be used to indicate which C++
 language standard to use (<code>-std=c++11</code> often doesn&#8217;t work well because newlib
 relies on some GNU extensions).</p>
 <h3 id="sdk-toolchains">SDK toolchains</h3>
 <p>The Native Client SDK includes multiple toolchains. It has one PNaCl toolchain
 and it has multiple GCC-based toolchains that are differentiated by target
 architectures and C libraries. The single PNaCl toolchain is located
 in a directory named <code>pepper_&lt;version&gt;/toolchain/&lt;OS_platform&gt;_pnacl</code>,
@@ skipping 265 matching lines @@
 <li>&lt;prefix&gt;readelf</li>
 <li>&lt;prefix&gt;size</li>
 <li>&lt;prefix&gt;strings</li>
 <li>&lt;prefix&gt;strip</li>
 </ul>
 <h3 id="compiling">Compiling</h3>
 <p>Compiling files with the GNU-based toolchain is similar to compiling
 files with the PNaCl-based toolchain, except that the output is
 architecture specific.</p>
 <p>For example, assuming you&#8217;re developing on a Windows machine, targeting the x86
-architecture, and using the newlib library, you can compile a 32-bit <strong>.nexe</strong>
-for the hello_world example with the following command:</p>
+architecture you can compile a 32-bit <strong>.nexe</strong> for the hello_world example with
+the following command:</p>
 <pre>
-nacl_sdk/pepper_&lt;version&gt;/toolchain/win_x86_newlib/bin/i686-nacl-gcc \
+nacl_sdk/pepper_&lt;version&gt;/toolchain/win_x86_glibc/bin/i686-nacl-gcc \
   hello_world.c -Inacl_sdk/pepper_&lt;version&gt;/include \
-  -Lnacl_sdk/pepper_&lt;version&gt;/lib/newlib/Release -o hello_world_x86_32.nexe \
+  -Lnacl_sdk/pepper_&lt;version&gt;/lib/glibc/Release -o hello_world_x86_32.nexe \
   -m32 -g -O2 -lppapi
 </pre>
 <p>To compile a 64-bit <strong>.nexe</strong>, you can run the same command but use -m64 instead
 of -m32. Alternatively, you could also use the version of the compiler that
 targets the x86-64 architecture, i.e., <code>x86_64-nacl-gcc</code>.</p>
 <p>You should name executable modules with a <strong>.nexe</strong> filename extension,
 regardless of what platform you&#8217;re using.</p>
 <h3 id="creating-libraries-and-linking">Creating libraries and Linking</h3>
 <p>Creating libraries and linking with the GNU-based toolchain is similar
 to doing the same with the PNaCl toolchain.  The relevant tools
 for creating <strong>static</strong> libraries are <code>&lt;prefix&gt;ar</code> and <code>&lt;prefix&gt;ranlib</code>.
 Linking can be done with <code>&lt;prefix&gt;g++</code>. See the
 <a class="reference internal" href="/native-client/devguide/devcycle/dynamic-loading.html"><em>Dynamic Linking &amp; Loading with glibc</em></a>
 section on how to create <strong>shared</strong> libraries.</p>
 <h3 id="finalizing-a-nexe-for-deployment">Finalizing a <strong>nexe</strong> for deployment</h3>
 <p>Unlike the PNaCl toolchain, no separate finalization step is required
 for <strong>nexe</strong> files. The <strong>nexe</strong> files are always in a <strong>stable</strong> format.
 However, the <strong>nexe</strong> file may contain debug information and symbol information
 which may make the <strong>nexe</strong> file larger than needed for distribution.
 To minimize the size of the distributed file, you can run the
 <code>&lt;prefix&gt;strip</code> tool to strip out debug information.</p>
 <h2 id="using-make">Using make</h2>
 <p>This document doesn&#8217;t cover how to use <code>make</code>, but if you want to use
 <code>make</code> to build your Native Client module, you can base your Makefile on the
 ones in the SDK examples.</p>
 <p>The Makefiles for the SDK examples build most of the examples in multiple
 configurations (using PNaCl vs NaCl, using different C libraries,
 targeting different architectures, and using different levels of optimization).
 To select a specific toolchain, set the <strong>environment variable</strong>
-<code>TOOLCHAIN</code> to either <code>pnacl</code>, <code>newlib</code>, <code>glibc</code>, or <code>host</code>.
+<code>TOOLCHAIN</code> to either <code>pnacl</code>, <code>clang-newlib</code>, <code>glibc</code>, or <code>host</code>.
 To select a specific level of optimization set the <strong>environment
 variable</strong> <code>CONFIG</code> to either <code>Debug</code>, or <code>Release</code>. Running
 <code>make</code> in each example&#8217;s directory does <strong>one</strong> of the following,
 depending on the setting of the environment variables.</p>
 <ul class="small-gap">
 <li><p class="first">If <code>TOOLCHAIN=pnacl</code> creates a subdirectory called <code>pnacl</code>;</p>
 <ul class="small-gap">
 <li>builds a <strong>.pexe</strong> (architecture-independent Native Client executable) using
 the newlib library</li>
 <li>generates a Native Client manifest (.nmf) file for the pnacl version of the
 example</li>
 </ul>
 </li>
-<li><p class="first">If <code>TOOLCHAIN=newlib</code> creates a subdirectory called <code>newlib</code>;</p>
+<li><p class="first">If <code>TOOLCHAIN=clang-newlib</code> creates a subdirectory called <code>clang-newlib</code>;</p>
 <ul class="small-gap">
 <li>builds <strong>.nexes</strong> for the x86-32, x86-64, and ARM architectures using the
-newlib library</li>
-<li>generates a Native Client manifest (.nmf) file for the newlib version of
-the example</li>
+nacl-clang toolchain and the newlib C library</li>
+<li>generates a Native Client manifest (.nmf) file for the clang-newlib version
+of the example</li>
 </ul>
 </li>
 <li><p class="first">If <code>TOOLCHAIN=glibc</code> creates a subdirectory called <code>glibc</code>;</p>
 <ul class="small-gap">
-<li>builds <strong>.nexes</strong> for the x86-32 and x86-64 architectures using the glibc
-library</li>
+<li>builds <strong>.nexes</strong> for the x86-32, x86-64 and ARM architectures using the
+glibc library</li>
 <li>generates a Native Client manifest (.nmf) file for the glibc version of the
 example</li>
 </ul>
 </li>
 <li><p class="first">If <code>TOOLCHAIN=host</code> creates a subdirectory called <code>windows</code>, <code>linux</code>,
 or <code>mac</code> (depending on your development machine);</p>
 <ul class="small-gap">
 <li>builds a Pepper plugin (.dll for Windows, .so for Linux/Mac) using the
 hosted toolchain on your development machine</li>
 <li>generates a Native Client manifest (.nmf) file for the host Pepper plugin
@@ skipping 24 matching lines @@
 libraries, such as libpthread and libc, plus the relevant header files.
 The standard libraries are located under the <code>/pepper_&lt;version&gt;</code> directory
 in the following locations:</p>
 <ul class="small-gap">
 <li>PNaCl toolchain: <code>toolchain/&lt;platform&gt;_pnacl/usr/lib</code></li>
 <li>x86 toolchains: <code>toolchain/&lt;platform&gt;_x86_&lt;c_library&gt;/x86_64-nacl/lib32</code> and
 <code>/lib64</code> (for the 32-bit and 64-bit target architectures, respectively)</li>
 <li>ARM toolchain: <code>toolchain/&lt;platform&gt;_arm_&lt;c_library&gt;/arm-nacl/lib</code></li>
 </ul>
 <p>For example, on Windows, the libraries for the x86-64 architecture in the
-newlib toolchain are in <code>toolchain/win_x86_newlib/x86_64-nacl/lib64</code>.</p>
+glibc toolchain are in <code>toolchain/win_x86_glibc/x86_64-nacl/lib64</code>.</p>
 <p>The header files are in:</p>
 <ul class="small-gap">
-<li>PNaCl toolchain: <code>toolchain/&lt;platform&gt;_pnacl/usr/include</code></li>
-<li>x86 toolchains: <code>toolchain/&lt;platform&gt;_x86_&lt;c_library&gt;/x86_64-nacl/include</code></li>
-<li>ARM toolchain: <code>toolchain/&lt;platform&gt;_arm_&lt;c_library&gt;/arm-nacl/include</code></li>
+<li>PNaCl toolchain: <code>toolchain/&lt;platform&gt;_pnacl/le32-nacl/include</code></li>
+<li>clang newlib toolchains: <code>toolchain/&lt;platform&gt;_pnacl/&lt;arch&gt;-nacl/include</code></li>
+<li>x86 glibc toolchain: <code>toolchain/&lt;platform&gt;_x86_glibc/x86_64-nacl/include</code></li>
+<li>ARM glibc toolchain: <code>toolchain/&lt;platform&gt;_arm_glibc/arm-nacl/include</code></li>
 </ul>
 <p>Many other libraries have been ported for use with Native Client; for more
 information, see the <a class="reference external" href="https://chromium.googlesource.com/webports">webports</a>
 project. If you port an open-source library for your own use, we recommend
 adding it to webports.</p>
 <p>Besides the standard libraries, the SDK includes Pepper libraries.
 The PNaCl Pepper libraries are located in the the
 <code>nacl_sdk/pepper_&lt;version&gt;/lib/pnacl/&lt;Release or Debug&gt;</code> directory.
 The GNU-based toolchain has Pepper libraries in
-<code>nacl_sdk/pepper_&lt;version&gt;/lib/newlib_&lt;arch&gt;/&lt;Release or Debug&gt;</code>
-and <code>nacl_sdk/pepper_&lt;version&gt;/lib/glibc_&lt;arch&gt;/&lt;Release or Debug&gt;</code>.
+<code>nacl_sdk/pepper_&lt;version&gt;/lib/glibc_&lt;arch&gt;/&lt;Release or Debug&gt;</code>
+and <code>nacl_sdk/pepper_&lt;version&gt;/lib/clang-newlib_&lt;arch&gt;/&lt;Release or Debug&gt;</code>.
 The libraries provided by the SDK allow the application to use Pepper,
 as well as convenience libraries to simplify porting an application that
 uses POSIX functions. Here are descriptions of the Pepper libraries provided
 in the SDK.</p>
 <dl class="docutils" id="devcycle-building-nacl-io">
 <dt>libppapi.a</dt>
 <dd>Implements the Pepper (PPAPI) C interface. Needed for all applications that
 use Pepper (even C++ applications).</dd>
 <dt>libppapi_cpp.a</dt>
 <dd>Implements the Pepper (PPAPI) C++ interface. Needed by C++ applications that
@@ skipping 82 matching lines @@
 Function foo has disallowed type: i128 (i128)
 LLVM ERROR: PNaCl ABI verification failed
 </pre>
 <p>When faced with a PNaCl ABI verification error, check the list of features
 that are <a class="reference internal" href="/native-client/nacl-and-pnacl.html#when-to-use-nacl"><em>not supported by PNaCl</em></a>.
 If the problem you face is not listed as restricted,
 <a class="reference internal" href="/native-client/help.html#help"><em>let us know</em></a>!</p>
 </section>
 
 {{/partials.standard_nacl_article}}