[pypy-svn] r79642 - in pypy/extradoc/pypy.org: . source

[arigo at codespeak.net]

Author: arigo
Date: Mon Nov 29 16:25:50 2010
New Revision: 79642

Modified:
   pypy/extradoc/pypy.org/download.html
   pypy/extradoc/pypy.org/source/download.txt
Log:
Updates.


Modified: pypy/extradoc/pypy.org/download.html
==============================================================================
--- pypy/extradoc/pypy.org/download.html	(original)
+++ pypy/extradoc/pypy.org/download.html	Mon Nov 29 16:25:50 2010
@@ -151,12 +151,16 @@
 requirement down to 1.2 GB on 32-bit, 2.4 GB on 64-bit.)
 You should just start by downloading an official release of PyPy (with the
 JIT).</li>
-<li>In the final step, which is compiling the generated C files, the <tt class="docutils literal">CFLAGS</tt>
-are passed to the compiler.  However, avoid passing too many custom
-<tt class="docutils literal">CFLAGS</tt>, particularly when compiling with <tt class="docutils literal">asmgcroot</tt> (needed by the
-JIT).  It will make <tt class="docutils literal">trackgcroot.py</tt> unhappy.  In case you want to try
-it out anyway, after a CompilationError you can change your <tt class="docutils literal">CFLAGS</tt>
-and retry by typing <tt class="docutils literal">cd <span class="pre">/tmp/usession-$USER/testing_1;</span> make</tt>.</li>
+<li>Because of <tt class="docutils literal">asmgcroot</tt>, compiling the generated C files containing the
+JIT is delicate.  It requires using either MSVC or gcc with no particularly
+fancy options.  It does not work e.g. with clang, or if you pass uncommon
+options with the <tt class="docutils literal">CFLAGS</tt> environment variable.  The generated C files
+are left around in <tt class="docutils literal"><span class="pre">/tmp/usession-$USER/testing_1/</span></tt>, so if compilation
+fails (i.e. you get a <tt class="docutils literal">CompilationError</tt>) or if you want to build a
+debug build, you can go there and retry running <tt class="docutils literal">make</tt>.  For example:
+<tt class="docutils literal">make <span class="pre">CFLAGS=&quot;&quot;</span></tt>, or <tt class="docutils literal">make lldebug</tt>.  It is recommended to move this
+directory away if you want to keep it; otherwise, further runs of
+<tt class="docutils literal">translate.py</tt> will remove it.</li>
 </ul>
 </div>
 <div class="section" id="checksums">

Modified: pypy/extradoc/pypy.org/source/download.txt
==============================================================================
--- pypy/extradoc/pypy.org/source/download.txt	(original)
+++ pypy/extradoc/pypy.org/source/download.txt	Mon Nov 29 16:25:50 2010
@@ -138,13 +138,16 @@
   You should just start by downloading an official release of PyPy (with the
   JIT).
 
-* In the final step, which is compiling the generated C files, the ``CFLAGS``
-  are passed to the compiler.  However, avoid passing too many custom
-  ``CFLAGS``, particularly when compiling with ``asmgcroot`` (needed by the
-  JIT).  It will make ``trackgcroot.py`` unhappy.  In case you want to try
-  it out anyway, after a CompilationError you can change your ``CFLAGS``
-  and retry by typing ``cd /tmp/usession-$USER/testing_1; make``.
-
+* Because of ``asmgcroot``, compiling the generated C files containing the
+  JIT is delicate.  It requires using either MSVC or gcc with no particularly
+  fancy options.  It does not work e.g. with clang, or if you pass uncommon
+  options with the ``CFLAGS`` environment variable.  The generated C files
+  are left around in ``/tmp/usession-$USER/testing_1/``, so if compilation
+  fails (i.e. you get a ``CompilationError``) or if you want to build a
+  debug build, you can go there and retry running ``make``.  For example:
+  ``make CFLAGS=""``, or ``make lldebug``.  It is recommended to move this
+  directory away if you want to keep it; otherwise, further runs of
+  ``translate.py`` will remove it.
 
 .. _`x86 (IA-32)`: http://en.wikipedia.org/wiki/IA-32
 .. _`x86-64`: http://en.wikipedia.org/wiki/X86-64