[NaCl SDK] docs: Remove references to obsolete debugging env vars.

Make also complained about some broken links and stopped w/
warnings as errors.

I assume a bunch these went away w/ the really old proxy switch =)

BUG=266395
NOTRY=true

Review URL: https://codereview.chromium.org/383523004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@282653 0039d316-1c4b-4281-b951-d872f2087c98

native_client_sdk/doc_generated/community/index.html

@@ -3,7 +3,7 @@
 <section id="community">
 <span id="id1"></span><h1 id="community"><span id="id1"></span>Community</h1>
 <p>This section contains pages related to the Native Client <em>community</em> - both
-<strong>implementors</strong> (contributors to the <a class="reference external" href="nacl_project_">open-source Native Client project</a>) and <strong>developers</strong>, who use Native Client to develop web
+<strong>implementors</strong> (contributors to the <a class="reference external" href="https://code.google.com/p/nativeclient/">open-source Native Client project</a>) and <strong>developers</strong>, who use Native Client to develop web
 applications.</p>
 <p>For a list of active forums where you can ask questions, check the
 <a class="reference internal" href="/native-client/help.html#help"><em>help page</em></a>.</p>

native_client_sdk/doc_generated/devguide/devcycle/debugging.html

@@ -74,10 +74,7 @@ application process, so look for the rendering rate there.</p>
 increase the amount of Native Client&#8217;s diagnostic output by setting the
 following <a class="reference external" href="http://en.wikipedia.org/wiki/Environment_variable">environment variables</a>:</p>
 <ul class="small-gap">
-<li>NACL_DEBUG_ENABLE=1</li>
-<li>PPAPI_BROWSER_DEBUG=1</li>
 <li>NACL_PLUGIN_DEBUG=1</li>
-<li>NACL_PPAPI_PROXY_DEBUG=1</li>
 <li>NACL_SRPC_DEBUG=[1-255] (use a higher number for more verbose debug output)</li>
 <li>NACLVERBOSITY=[1-255]</li>
 </ul>

native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html

@@ -318,7 +318,8 @@ the list of shared library dependencies using tools such as <code>objdump_</code
 executable code modules that the application directly depends on, including
 modules from the application itself (.nexe and .so files), modules from the
 Native Client SDK (e.g., libppapi_cpp.so), and perhaps also modules from
-<a class="reference external" href="naclports_">naclport</a> or from <a class="reference external" href="../../community/middleware">middleware systems</a> that
+<a class="reference external" href="http://code.google.com/p/naclports/">naclports</a> or from
+<a class="reference external" href="../../community/middleware">middleware systems</a> that
 the application uses. You must provide all of those modules as part of the
 application deployment process.</p>
 <p>As explained in <a class="reference internal" href="/native-client/devguide/distributing.html"><em>Distributing Your Application</em></a>, there are two basic ways to deploy an application:</p>

native_client_sdk/doc_generated/faq.html

@@ -226,7 +226,7 @@ for an <a class="reference external" href="https://www.google.com/search?q=gcc+i
 <section id="is-native-client-open-is-it-a-standard">
 <h3 id="is-native-client-open-is-it-a-standard">Is Native Client open? Is it a standard?</h3>
 <p>Native Client is completely open: the executable format is open and the
-<a class="reference external" href="nacl_project_">source code is open</a>. Right
+<a class="reference external" href="https://code.google.com/p/nativeclient/">source code is open</a>. Right
 now the Native Client project is in its early stages, so it&#8217;s premature
 to consider Native Client for standardization.</p>
 <p>We consistenly try to document our design and implementation and hope to

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

@@ -52,10 +52,7 @@ increase the amount of Native Client's diagnostic output by setting the
 following `environment variables
 <http://en.wikipedia.org/wiki/Environment_variable>`_:
 
-* NACL_DEBUG_ENABLE=1
-* PPAPI_BROWSER_DEBUG=1
 * NACL_PLUGIN_DEBUG=1
-* NACL_PPAPI_PROXY_DEBUG=1
 * NACL_SRPC_DEBUG=[1-255] (use a higher number for more verbose debug output)
 * NACLVERBOSITY=[1-255]
 

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

@@ -307,7 +307,8 @@ As described above, an application's manifest file must explicitly list all the
 executable code modules that the application directly depends on, including
 modules from the application itself (.nexe and .so files), modules from the
 Native Client SDK (e.g., libppapi_cpp.so), and perhaps also modules from
-`naclport <naclports_>`_ or from `middleware systems <../../community/middleware>`_ that
+`naclports <http://code.google.com/p/naclports/>`_ or from
+`middleware systems <../../community/middleware>`_ that
 the application uses. You must provide all of those modules as part of the
 application deployment process.
 

native_client_sdk/src/doc/faq.rst

@@ -192,7 +192,7 @@ Is Native Client open? Is it a standard?
 ----------------------------------------
 
 Native Client is completely open: the executable format is open and the
-`source code is open <nacl_project_>`_. Right
+`source code is open <https://code.google.com/p/nativeclient/>`_. Right
 now the Native Client project is in its early stages, so it's premature
 to consider Native Client for standardization.
 

ppapi/native_client/tools/browser_tester/browsertester/browserlauncher.py

@@ -78,9 +78,7 @@ def MakeEnv(options):
   # Enable PPAPI Dev interfaces for testing.
   env['NACL_ENABLE_PPAPI_DEV'] = str(options.enable_ppapi_dev)
   if options.debug:
-    env['PPAPI_BROWSER_DEBUG'] = '1'
     env['NACL_PLUGIN_DEBUG'] = '1'
-    env['NACL_PPAPI_PROXY_DEBUG'] = '1'
     # env['NACL_SRPC_DEBUG'] = '1'
   return env