PNaClize and update the 'Devguide -> Running' page of the documentation.

native_client_sdk/src/doc/devguide/devcycle/building.rst

 .. _devcycle-building:
 
 ########
 Building
 ########
 
 .. contents:: Table Of Contents
   :local:
   :backlinks: none
   :depth: 2
@@ skipping 76 matching lines @@
 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 ``toolchain/<OS_platform>_pnacl``, and the GCC-based
 toolchains are located in directories named
 ``toolchain/<OS_platform>_<architecture>_<library>``, where:
 
 * *<platform>* is the platform of your development machine (win, mac, or linux)
 * *<architecture>* is your target architecture (x86 or arm)
 * *<library>* is the C library you are compiling with (newlib or glibc)
 
-The compilers, linkers, and other tools are located in the ``bin/`` 
+The compilers, linkers, and other tools are located in the ``bin/``
 subdirectory in each toolchain. For example, the tools in the Windows SDK
 for PNaCl has a C++ compiler in ``toolchain/win_pnacl/bin/pnacl-clang++``.
 As another example, the GCC-based C++ compiler that targets the x86 and uses the
 newlib library, is located at ``toolchain/win_x86_newlib/bin/x86_64-nacl-g++``.
 
 .. Note::
   :class: note
 
   The SDK toolchains descend from the ``toolchain/`` directory. The SDK also
   has a ``tools/`` directory; this directory contains utilities that are not
@@ skipping 505 matching lines @@
 Here is one way to find the appropriate library for a given symbol:
 
 .. naclcode::
   :prettyprint: 0
 
   <NACL_SDK_ROOT>/toolchain/<platform>_pnacl/bin/pnacl-nm -o \
     toolchain/<platform>_pnacl/usr/lib/*.a | grep <MySymbolName>
 
 .. TODO(jvoung): Add some notes about debugging GNU-extensions not
 .. supported by PNaCl ABI stabilization passes, like computed gotos?