projects
/
ghc-hetmet.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
c6c423e
)
Update bundle installation instructions
author
Ian Lynagh
<igloo@earth.li>
Fri, 13 Jul 2007 19:44:24 +0000
(19:44 +0000)
committer
Ian Lynagh
<igloo@earth.li>
Fri, 13 Jul 2007 19:44:24 +0000
(19:44 +0000)
docs/users_guide/installing.xml
patch
|
blob
|
history
diff --git
a/docs/users_guide/installing.xml
b/docs/users_guide/installing.xml
index
dc0251a
..
42023a9
100644
(file)
--- a/
docs/users_guide/installing.xml
+++ b/
docs/users_guide/installing.xml
@@
-76,10
+76,11
@@
Then you should find the bundle contents inside a single directory,
<para>
OK, so let's assume that you have unpacked your chosen bundles. What
<para>
OK, so let's assume that you have unpacked your chosen bundles. What
-next? Well, you will at least need to run the
+next? Well, you will first need to
<literal>configure</literal><indexterm><primary>configure</primary></indexterm>
<literal>configure</literal><indexterm><primary>configure</primary></indexterm>
-script by changing directory into the top-level directory for the
-bundle and typing <literal>./configure</literal>. That should convert
+the bundle by
+changing to the bundle's top-level directory
+and typing <literal>./configure</literal>. That should convert
<literal>Makefile-vars.in</literal> to <literal>Makefile-vars</literal>.
</para>
<literal>Makefile-vars.in</literal> to <literal>Makefile-vars</literal>.
</para>
@@
-95,7
+96,7
@@
To see all the flags that configure accepts, run
</para>
<para>
</para>
<para>
-To install a package, you'll have to do the following:
+Then do the following:
</para>
<para>
</para>
<para>
@@
-108,27
+109,31
@@
Run <literal>make install</literal>. This <emphasis>
should</emphasis> work with ordinary Unix
<literal>make</literal>—no need for fancy stuff like GNU
<literal>make</literal>.
should</emphasis> work with ordinary Unix
<literal>make</literal>—no need for fancy stuff like GNU
<literal>make</literal>.
-
</para>
</listitem>
</para>
</listitem>
-<listitem>
+<listitem>
<para>
<para>
-<literal>rehash</literal> (t?csh or zsh users), so your shell will see the new
-stuff in your bin directory.
-
+If appropriate, add the bin directory to your PATH, as instructed.
</para>
</listitem>
</para>
</listitem>
+
<listitem>
<listitem>
+<para>
+You may need to run <literal>rehash</literal> (t?csh or zsh users), in
+order for your shell to see the new stuff in your bin directory.
+</para>
+</listitem>
+<listitem>
<para>
Once done, test your “installation” as suggested in
<xref linkend="GHC-test"/>. Be sure to use a <literal>-v</literal>
option, so you can see exactly what pathnames it's using.
<para>
Once done, test your “installation” as suggested in
<xref linkend="GHC-test"/>. Be sure to use a <literal>-v</literal>
option, so you can see exactly what pathnames it's using.
-
If things don't work as expected, check the list of known pitfalls in
the <ulink url="http://hackage.haskell.org/trac/ghc/wiki/Building">building guide</ulink>.
</para>
If things don't work as expected, check the list of known pitfalls in
the <ulink url="http://hackage.haskell.org/trac/ghc/wiki/Building">building guide</ulink>.
</para>
+
</listitem>
</orderedlist>
</listitem>
</orderedlist>