<varlistentry>
<term>
+ <option>-eventlog</option>
+ <indexterm><primary><option>-eventlog</option></primary></indexterm>
+ </term>
+ <listitem>
+ <para>
+ Link the program with the "eventlog" version of the
+ runtime system. A program linked in this way can generate
+ a runtime trace of events (such as thread start/stop) to a
+ binary file
+ <literal><replaceable>program</replaceable>.eventlog</literal>,
+ which can then be interpreted later by various tools. See
+ <xref linkend="rts-eventlog" /> for more information.
+ </para>
+ <para>
+ <option>-eventlog</option> can be used
+ with <option>-threaded</option>. It is implied
+ by <option>-debug</option>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>
<option>-fno-gen-manifest</option>
<indexterm><primary><option>-fno-gen-manifest</option></primary>
</indexterm>
library entirely.</para>
</listitem>
</varlistentry>
+
+ <varlistentry>
+ <term>
+ <option>-dylib-install-name <replaceable>path</replaceable></option>
+ <indexterm><primary><option>-dylib-install-name</option></primary>
+ </indexterm>
+ </term>
+ <listitem>
+ <para>On Darwin/MacOS X, dynamic libraries are stamped at build time with an
+ "install name", which is the ultimate install path of the library file.
+ Any libraries or executables that subsequently link against it will pick
+ up that path as their runtime search location for it. By default, ghc sets
+ the install name to the location where the library is built. This option
+ allows you to override it with the specified file path. (It passes
+ <literal>-install_name</literal> to Apple's linker.) Ignored on other
+ platforms.</para>
+ </listitem>
+ </varlistentry>
</variablelist>
</sect2>