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 <ttclass="docutils literal">CFLAGS</tt> environment variable. The generated C files
are left around in <ttclass="docutils literal"><spanclass="pre">/tmp/usession-$USER/testing_1/</span></tt>, so if compilation
are left around in <ttclass="docutils literal"><spanclass="pre">/tmp/usession-$USER/testing_1/</span></tt> or
<ttclass="docutils literal"><spanclass="pre">$TMPDIR/usession-$USER/testing_1</span></tt>, so if compilation
fails (i.e. you get a <ttclass="docutils literal">CompilationError</tt>) or if you want to build a
debug build, you can go there and retry running <ttclass="docutils literal">make</tt>. For example:
...
...
@@ -159,7 +160,7 @@
fails (i.e. you get a <ttclass="docutils literal">CompilationError</tt>) or if you want to build a
debug build, you can go there and retry running <ttclass="docutils literal">make</tt>. For example:
<ttclass="docutils literal">make <spanclass="pre">CFLAGS=""</span></tt>, or <ttclass="docutils literal">make lldebug</tt>. It is recommended to move this
directory away if you want to keep it; otherwise, further runs of
<ttclass="docutils literal">CFLAGS= make</tt>, or <ttclass="docutils literal">make lldebug</tt>. It is recommended to move this
directory away if you want to keep it; otherwise, future runs of
<ttclass="docutils literal">translate.py</tt> will remove it.</li>