summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorKirsten Chevalier <chevalier@alum.wellesley.edu>2007-02-07 08:45:27 +0000
committerKirsten Chevalier <chevalier@alum.wellesley.edu>2007-02-07 08:45:27 +0000
commit8d276febb7e186affdcd9fa39f5a185a2e15847e (patch)
treed2ed00a4eea6e5b0206e7ee5df450e6a45a77770 /docs
parent5ddee764beb312933256096d03df7c3ec47ac452 (diff)
downloadhaskell-8d276febb7e186affdcd9fa39f5a185a2e15847e.tar.gz
Update to manual section for ticky-ticky
I added a slightly more helpful remark in the profiling section of the manual about how to use ticky-ticky.
Diffstat (limited to 'docs')
-rw-r--r--docs/users_guide/profiling.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/users_guide/profiling.xml b/docs/users_guide/profiling.xml
index c30bd803b5..fb6049dc6e 100644
--- a/docs/users_guide/profiling.xml
+++ b/docs/users_guide/profiling.xml
@@ -1327,9 +1327,9 @@ to re-read its input file:
profiling system, intended for all users everywhere.</para>
<para>To be able to use ticky-ticky profiling, you will need to
- have built appropriate libraries and things when you made the
- system. See &ldquo;Customising what libraries to build,&rdquo; in
- the installation guide.</para>
+ have built the ticky RTS. (This should be described in
+ the building guide, but amounts to building the RTS with way
+ "t" enabled.)</para>
<para>To get your compiled program to spit out the ticky-ticky
numbers, use a <option>-r</option> RTS