[NaCl SDK] Remove references to naclports bundle

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

 .. _devcycle-building:
 
 ########
 Building
 ########
 
 .. contents:: Table Of Contents
   :local:
   :backlinks: none
   :depth: 2
@@ skipping 563 matching lines @@
 For example, on Windows, the libraries for the x86-64 architecture in the
 newlib toolchain are in ``toolchain/win_x86_newlib/x86_64-nacl/lib64``.
 
 The header files are in:
 
 * PNaCl toolchain: ``toolchain/<platform>_pnacl/usr/include``
 * x86 toolchains: ``toolchain/<platform>_x86_<c_library>/x86_64-nacl/include``
 * ARM toolchain: ``toolchain/<platform>_arm_<c_library>/arm-nacl/include``
 
 Many other libraries have been ported for use with Native Client; for more
-information, see the `naclports <http://code.google.com/p/naclports/>`_
+information, see the `webports <https://chromium.googlesource.com/webports>`_
 project. If you port an open-source library for your own use, we recommend
-adding it to naclports.
+adding it to webports.
 
 Besides the standard libraries, the SDK includes Pepper libraries.
 The PNaCl Pepper libraries are located in the the
 ``nacl_sdk/pepper_<version>/lib/pnacl/<Release or Debug>`` directory.
 The GNU-based toolchain has Pepper libraries in
 ``nacl_sdk/pepper_<version>/lib/newlib_<arch>/<Release or Debug>``
 and ``nacl_sdk/pepper_<version>/lib/glibc_<arch>/<Release or Debug>``.
 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
@@ skipping 29 matching lines @@
   details see ``include/ppapi_simple/ps.h``. For an example of
   how to use ppapi_simple, ``see examples/tutorial/using_ppapi_simple``.
 
 
 .. Note::
   :class: note
 
   * Since the Native Client toolchains use their own library and header search
     paths, the tools won't find third-party libraries you use in your
     non-Native-Client development. If you want to use a specific third-party
-    library for Native Client development, look for it in `naclports
-    <http://code.google.com/p/naclports/>`_, or port the library yourself.
+    library for Native Client development, look for it in `webports
+    <https://chromium.googlesource.com/webports>`_, or port the library yourself.
   * The order in which you list libraries in your build commands is important,
     since the linker searches and processes libraries in the order in which they
     are specified. See the ``\*_LDFLAGS`` variables in the Makefiles of the SDK
     examples for the order in which specific libraries should be listed.
 
 Troubleshooting
 ===============
 
 Some common problems, and how to fix them:
 
@@ skipping 65 matching lines @@
   Function foo has disallowed type: i128 (i128)
   LLVM ERROR: PNaCl ABI verification failed
 
 When faced with a PNaCl ABI verification error, check the list of features
 that are :ref:`not supported by PNaCl <when-to-use-nacl>`.
 If the problem you face is not listed as restricted,
 :ref:`let us know <help>`!
 
 .. _glibc: http://www.gnu.org/software/libc/
 .. _newlib: http://sourceware.org/newlib/