[NaCl SDK] Cleanup references to old newlib toolchain

native_client_sdk/src/doc/devguide/devcycle/dynamic-loading.rst

 ######################################
 Dynamic Linking and Loading with glibc
 ######################################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
 .. Note::
@@ skipping 93 matching lines @@
 
 SDK toolchains
 --------------
 
 The Native Client SDK contains multiple toolchains, which are differentiated by
 :ref:`target architecture <target_architectures>` and C library:
 
 =================== ========= ===============================
 Target architecture C library Toolchain directory
 =================== ========= ===============================
-x86                 newlib    toolchain/<platform>_x86_newlib
 x86                 glibc     toolchain/<platform>_x86_glibc
-ARM                 newlib    toolchain/<platform>_arm_newlib
+ARM                 glibc     toolchain/<platform>_arm_glibc
+x86                 newlib    toolchain/<platform>_pnacl
+ARM                 newlib    toolchain/<platform>_pnacl
 PNaCl               newlib    toolchain/<platform>_pnacl
 =================== ========= ===============================
 
 In the directories listed above, <platform> is the platform of your development
 machine (i.e., win, mac, or linux). For example, in the Windows SDK, the x86
 toolchain that uses glibc is in ``toolchain/win_x86_glibc``.
 
 .. Note::
   :class: note
 
-  **Note:** The ARM and PNaCl toolchains are currently restricted to newlib.
+  **Note:** The PNaCl toolchain is currently restricted to newlib.
 
 To use the glibc library and dynamic linking in your application, you **must**
-use a glibc toolchain. (Currently the only glibc toolchain is
-``<platform>_x86_glibc``.) Note that you must build all code in your application
+use a glibc toolchain.  Note that you must build all code in your application
 with one toolchain. Code from multiple toolchains cannot be mixed.
 
 Specifying and delivering shared libraries
 ------------------------------------------
 
 One significant difference between newlib and glibc applications is that glibc
 applications must explicitly list and deploy the shared libraries that they
 use.
 
 In a desktop environment, when the user launches a dynamically linked
@@ skipping 57 matching lines @@
   into a Native Client executable (.nexe).
 
 Run ``make`` in the dlopen directory to see the commands the Makefile executes
 to build x86 32-bit and 64-bit .nexe and .so files, and to generate a .nmf
 file. These commands are described below.
 
 .. Note::
   :class: note
 
   **Note:** The Makefiles for most of the examples in the SDK build the
-  examples using multiple toolchains (x86 newlib, x86 glibc, ARM, and PNaCl).
-  With a few exceptions (listed in the :ref:`Release Notes
+  examples using multiple toolchains (x86 newlib, x86 glibc, ARM newlib, ARM
+  glibc, and PNaCl).  With a few exceptions (listed in the :ref:`Release Notes
   <sdk-release-notes>`), running "make" in each example's directory builds
   multiple versions of the example using the SDK toolchains. The dlopen example
   is one of those exceptions – it is only built with the x86 glibc toolchain,
   as that is currently the only toolchain that supports glibc and thus dynamic
   linking and loading. Take a look at the example Makefiles and the generated
   .nmf files for details on how to build dynamically linked applications.
 
 .. _dynamic_loading_manifest:
 
 Generating a Native Client manifest file for a dynamically linked application
@@ skipping 208 matching lines @@
 **undefined reference to 'dlopen' collect2: ld returned 1 exit status**
   This is a linker ordering problem that usually results from improper ordering
   of command line flags when linking. Reconfigure your command line string to
   list libraries after the -o flag.
 
 .. |menu-icon| image:: /images/menu-icon.png
 .. _objdump: http://en.wikipedia.org/wiki/Objdump
 .. _GLIBC: http://www.gnu.org/software/libc/index.html
 .. _POSIX: http://en.wikipedia.org/wiki/POSIX
 .. _newlib: http://sourceware.org/newlib/