Skip to content
Snippets Groups Projects
Commit 8fc63848 authored by sof's avatar sof
Browse files

[project @ 1997-07-27 09:13:43 by sof]

Updated for 2.05
parent b1ec105c
No related branches found
No related tags found
No related merge requests found
% Building and installing the Glasgow Functional Programming Tools Suite % Building and installing the Glasgow Functional Programming Tools Suite
% %
% Version 2.04 % Version 2.05
% June 1997 % July 1997
\begin{onlystandalone} \begin{onlystandalone}
\documentstyle[11pt,literate]{article} \documentstyle[11pt,literate]{article}
\begin{document} \begin{document}
\title{Building and installing the Glasgow Functional Programming Tools Suite\\ \title{Building and installing the Glasgow Functional Programming Tools Suite\\
Version~2.04} Version~2.05}
\author{The GHC Team\\ \author{The GHC Team\\
Department of Computing Science\\ Department of Computing Science\\
University of Glasgow\\ University of Glasgow\\
...@@ -84,8 +84,8 @@ confidence will work well by having tested it (more) thoroughly. ...@@ -84,8 +84,8 @@ confidence will work well by having tested it (more) thoroughly.
Source-only distributions are either bugfix releases or snapshots of Source-only distributions are either bugfix releases or snapshots of
current state of development. The release has undergone some testing. current state of development. The release has undergone some testing.
GHC~2.04 is a source-only release, and it can be compiled up using GHC~2.05 is a source-only release, and it can be compiled up using
either GHC~2.02 (or the bugfix release, GHC~2.03) or the Good Old either GHC~2.02 (or subsequent bugfix releases) or the Good Old
Compiler, GHC~0.29. Compiling with 0.29 is recommended if you're Compiler, GHC~0.29. Compiling with 0.29 is recommended if you're
a performance junkie, as 0.29 (still) generates zippier code, but a performance junkie, as 0.29 (still) generates zippier code, but
GHC~2.04 is catching up. GHC~2.04 is catching up.
...@@ -179,7 +179,7 @@ If in doubt, please send a message to \tr{glasgow-haskell-bugs@dcs.gla.ac.uk}. ...@@ -179,7 +179,7 @@ If in doubt, please send a message to \tr{glasgow-haskell-bugs@dcs.gla.ac.uk}.
%************************************************************************ %************************************************************************
%* * %* *
\section[port-info]{What machines the Glasgow tools, version~2.04, run on} \section[port-info]{What machines the Glasgow tools, version~2.05, run on}
\index{ports, GHC} \index{ports, GHC}
\index{GHC ports} \index{GHC ports}
\index{supported platforms} \index{supported platforms}
...@@ -226,7 +226,7 @@ unsurprisingly. Both have native-code generators, for quicker ...@@ -226,7 +226,7 @@ unsurprisingly. Both have native-code generators, for quicker
compilations. The native-code generator for iX86 platforms (e.g., compilations. The native-code generator for iX86 platforms (e.g.,
Linux ELF) is {\em nearly} working; but is not turned on by default. Linux ELF) is {\em nearly} working; but is not turned on by default.
Here's everything that's known about GHC ports, as of 2.04. We Here's everything that's known about GHC ports, as of 2.05. We
identify platforms by their ``canonical'' CPU/Manufacturer/OS triple. identify platforms by their ``canonical'' CPU/Manufacturer/OS triple.
Note that some ports are fussy about which GCC version you use; or Note that some ports are fussy about which GCC version you use; or
...@@ -267,7 +267,7 @@ Concurrent/Parallel Haskell probably don't work (yet). ...@@ -267,7 +267,7 @@ Concurrent/Parallel Haskell probably don't work (yet).
%------------------------------------------------------------------- %-------------------------------------------------------------------
\item[\tr{i386-*-linux} (PCs running Linux---ELF format):] \item[\tr{i386-*-linux} (PCs running Linux---ELF format):]
\index{i386-*-linux: registerised port} \index{i386-*-linux: registerised port}
GHC~2.04 works registerised. GHC~2.05 works registerised.
You {\em must} have GCC 2.7.x or later. You {\em must} have GCC 2.7.x or later.
The iX86 native-code generator is {\em nearly} there, but it The iX86 native-code generator is {\em nearly} there, but it
isn't turned on by default. isn't turned on by default.
...@@ -284,7 +284,7 @@ On old Linux a.out systems: should be the same. ...@@ -284,7 +284,7 @@ On old Linux a.out systems: should be the same.
%------------------------------------------------------------------- %-------------------------------------------------------------------
\item[\tr{i386-*-freebsd} (PCs running FreeBSD 2.2 or higher, and \item[\tr{i386-*-freebsd} (PCs running FreeBSD 2.2 or higher, and
NetBSD/OpenBSD using FreeBSD emulation):] \index{i386-*-freebsd: NetBSD/OpenBSD using FreeBSD emulation):] \index{i386-*-freebsd:
registerised port} GHC~2.04 works registerised. Supports same set of registerised port} GHC~2.05 works registerised. Supports same set of
bundles as the above. bundles as the above.
\index{i386-*-freebsd: profiling---yes} \index{i386-*-freebsd: profiling---yes}
...@@ -306,7 +306,7 @@ Profiling works, so does Concurrent Haskell. ...@@ -306,7 +306,7 @@ Profiling works, so does Concurrent Haskell.
%------------------------------------------------------------------- %-------------------------------------------------------------------
\item[\tr{mips-sgi-irix5}:] \item[\tr{mips-sgi-irix5}:]
\index{mips-sgi-irix5: registerised port} \index{mips-sgi-irix5: registerised port}
GHC~2.04 works registerised (no native-code generator). GHC~2.05 works registerised (no native-code generator).
I suspect any GCC~2.6.x (or later) is OK. The GCC that I used I suspect any GCC~2.6.x (or later) is OK. The GCC that I used
was built with \tr{--with-gnu-as}; turns out that is important! was built with \tr{--with-gnu-as}; turns out that is important!
...@@ -320,7 +320,7 @@ Profiling might work, but it is untested. ...@@ -320,7 +320,7 @@ Profiling might work, but it is untested.
\item[\tr{mips-sgi-irix6}:] \item[\tr{mips-sgi-irix6}:]
\index{mips-sgi-irix6: registerised port} \index{mips-sgi-irix6: registerised port}
Thanks to the fine efforts of Tomasz Cholewo Thanks to the fine efforts of Tomasz Cholewo
\tr{<tjchol01@mecca.spd.louisville.edu>}, GHC~2.04 works registerised \tr{<tjchol01@mecca.spd.louisville.edu>}, GHC~2.05 works registerised
(no native code generator) under IRIX 6.2 and 6.3. Depends on having (no native code generator) under IRIX 6.2 and 6.3. Depends on having
specially tweaked version of gcc-2.7.2 around, which can be downloaded specially tweaked version of gcc-2.7.2 around, which can be downloaded
from from
...@@ -337,7 +337,7 @@ Profiling works, Concurrent/Parallel Haskell might work (AFAIK, untested). ...@@ -337,7 +337,7 @@ Profiling works, Concurrent/Parallel Haskell might work (AFAIK, untested).
%------------------------------------------------------------------- %-------------------------------------------------------------------
\item[\tr{powerpc-ibm-aix}:] \item[\tr{powerpc-ibm-aix}:]
\index{powerpc-ibm-aix: registerised port} \index{powerpc-ibm-aix: registerised port}
GHC~2.04 works registerised (no native-code generator..yet). GHC~2.05 works registerised (no native-code generator..yet).
I suspect 2.7.x is what you need together with this. I suspect 2.7.x is what you need together with this.
Concurrent/Parallel Haskell probably don't work (yet). Concurrent/Parallel Haskell probably don't work (yet).
...@@ -370,7 +370,7 @@ Concurrent/Parallel Haskell probably won't work (yet). ...@@ -370,7 +370,7 @@ Concurrent/Parallel Haskell probably won't work (yet).
%------------------------------------------------------------------- %-------------------------------------------------------------------
\item[\tr{m68k-sun-sunos4} (Sun3):] \item[\tr{m68k-sun-sunos4} (Sun3):]
\index{m68k-sun-sunos4: registerised port} \index{m68k-sun-sunos4: registerised port}
GHC~2.04 hasn't been tried on a Sun3. GHC~0.26 worked registerised. GHC~2.05 hasn't been tried on a Sun3. GHC~0.26 worked registerised.
No native-code generator. No native-code generator.
Concurrent/Parallel Haskell probably don't work (yet). Concurrent/Parallel Haskell probably don't work (yet).
...@@ -528,7 +528,7 @@ should always invoke @GHC@ version 2.02. ...@@ -528,7 +528,7 @@ should always invoke @GHC@ version 2.02.
\subsection{What bundles there are} \subsection{What bundles there are}
There are plenty of ``non-basic'' GHC bundles. The files for them are There are plenty of ``non-basic'' GHC bundles. The files for them are
called \tr{ghc-2.04-<bundle>-<platform>.tar.gz}, where the called \tr{ghc-2.05-<bundle>-<platform>.tar.gz}, where the
\tr{<platform>} is as above, and \tr{<bundle>} is one of these: \tr{<platform>} is as above, and \tr{<bundle>} is one of these:
\begin{description} \begin{description}
\item[\tr{prof}:] Profiling with cost-centres. You probably want this. \item[\tr{prof}:] Profiling with cost-centres. You probably want this.
...@@ -571,7 +571,7 @@ main = putStr "Hello, world!\n" ...@@ -571,7 +571,7 @@ main = putStr "Hello, world!\n"
First, give yourself a convenient way to execute the driver script First, give yourself a convenient way to execute the driver script
\tr{ghc/driver/ghc}, perhaps something like... \tr{ghc/driver/ghc}, perhaps something like...
\begin{verbatim} \begin{verbatim}
% ln -s /local/src/ghc-2.04/ghc/driver/ghc ~/bin/alpha/ghc % ln -s /local/src/ghc-2.05/ghc/driver/ghc ~/bin/alpha/ghc
% rehash % rehash
\end{verbatim} \end{verbatim}
...@@ -1726,7 +1726,7 @@ installation, this bug also suggests that you have an old GCC. ...@@ -1726,7 +1726,7 @@ installation, this bug also suggests that you have an old GCC.
\item \item
You {\em may} need to re-\tr{ranlib} your libraries (on Sun4s). You {\em may} need to re-\tr{ranlib} your libraries (on Sun4s).
\begin{verbatim} \begin{verbatim}
% cd $(libdir)/ghc-2.04/sparc-sun-sunos4 % cd $(libdir)/ghc-2.05/sparc-sun-sunos4
% foreach i ( `find . -name '*.a' -print` ) # or other-shell equiv... % foreach i ( `find . -name '*.a' -print` ) # or other-shell equiv...
? ranlib $i ? ranlib $i
? # or, on some machines: ar s $i ? # or, on some machines: ar s $i
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment