symbols are defined by your local GHC installation, the following
trick is useful:</para>
-<screen>
- $ ghc -E -optP-dM -cpp foo.hs
- $ cat foo.hspp
-</screen>
+<screen>$ ghc -E -optP-dM -cpp foo.hs
+$ cat foo.hspp</screen>
<para>(you need a file <filename>foo.hs</filename>, but it isn't
actually used).</para>
<varlistentry>
<term>
- <constant><replaceable>os</replaceable>_TARGET_OS=1</constant>
+ <constant><replaceable>os</replaceable>_OS=1</constant>
</term>
<listitem>
<para>This define allows conditional compilation based on
<varlistentry>
<term>
- <constant><replaceable>arch</replaceable>_TARGET_ARCH=1</constant>
+ <constant><replaceable>arch</replaceable>_ARCH=1</constant>
</term>
<listitem>
<para>This define allows conditional compilation based on
gaps vs -cpp</primary></indexterm>. In other words, strings
such as the following:</para>
-rogramlisting>
-rmod = "\
-p \
-"
-programlisting>
+<programlisting>strmod = "\
+\ p \
+\ "</programlisting>
<para>don't work with <option>-cpp</option>;
<filename>/usr/bin/cpp</filename> elides the backslash-newline
way to do this, but you can use this hack from the
command-line:</para>
-creen>
-ghc -c '-#include <X/Xlib.h>' Xstuff.lhs
-screen>
+<screen>% ghc -c '-#include <X/Xlib.h>' Xstuff.lhs</screen>
</sect2>