Home My Page Projects Code Snippets Project Openings SML/NJ
Summary Activity Forums Tracker Lists Tasks Docs Surveys News SCM Files

SCM Repository

[smlnj] Diff of /sml/trunk/INSTALL
ViewVC logotype

Diff of /sml/trunk/INSTALL

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1261, Tue Jul 23 15:45:45 2002 UTC revision 1414, Thu Nov 6 17:54:56 2003 UTC
# Line 1  Line 1 
1  Installation instructions for SML/NJ  Installation instructions for SML/NJ
2  ------------------------------------  ------------------------------------
3    
4  These are instructions for installing recent "working" versions of SML/NJ.  These are instructions for installing recent "working" versions of SML/NJ
5    on Unix-like systems, including MacOX X with the developer tools installed.
6    
7    If you are running MacOS X but don't have the developer tools, you can
8    install the system starting from the disk image that we provide.  See
9    MACOSXINSTALL for details.
10    
11    If you are running Win32, see WININSTALL.
12    
13  1. If you are in a hurry (and you have network connectivity) ...  1. If you are in a hurry (and you have network connectivity) ...
14  ----------------------------------------------------------------  ----------------------------------------------------------------
# Line 15  Line 22 
22     - Download config.tgz, e.g.     - Download config.tgz, e.g.
23    
24        $ v=110.38               # or whatever is the version you desire        $ v=110.38               # or whatever is the version you desire
25        $ wget http://ftp.research.bell-labs.com/dist/smlnj/working/$v/config.tgz        $ wget http://smlnj.cs.uchicago.edu/dist/working/$v/config.tgz
26    
27     - Gunzip and untar, e.g.     - Gunzip and untar, e.g.
28    
# Line 116  Line 123 
123     2.3.  Using a different ftp server (for a step-1.-like installation)     2.3.  Using a different ftp server (for a step-1.-like installation)
124     --------------------------------------------------------------------     --------------------------------------------------------------------
125    
126      - If you have a local mirror for ftp.research.bell-labs.com/dist/smlnj,      - If you have a local mirror for smlnj.cs.uchicago.edu/dist,
127        then you can speed up installation by pointing the automatic URL        then you can speed up installation by pointing the automatic URL
128        fetch mechanism there.  The URL of the repository is stored in        fetch mechanism there.  The URL of the repository is stored in
129        config/srcarchiveurl.  Edit this file before running config/install.sh.        config/srcarchiveurl.  Edit this file before running
130          config/install.sh.
131    
132     2.4.  Using locally stored tarballs     2.4.  Using locally stored tarballs
133     -----------------------------------     -----------------------------------
# Line 130  Line 138 
138            file:///usr/src/packages/smlnj/working/110.38            file:///usr/src/packages/smlnj/working/110.38
139    
140        (In other words, the URL should spell out the name of the local        (In other words, the URL should spell out the name of the local
141        directory that happens to contain the tarballs.)        directory that happens to contain the tarballs.  Notice that
142          this method does not seem to work with certain versions of wget
143          which do not understand the file:// scheme.)
144    
145     2.5.  What needs to be on my PATH?     2.5.  What needs to be on my PATH?
146     ----------------------------------     ----------------------------------
# Line 180  Line 190 
190     2.8 Forcing the installer to use a particular URL getter program     2.8 Forcing the installer to use a particular URL getter program
191     ----------------------------------------------------------------     ----------------------------------------------------------------
192    
193     By default, config/install.sh will attempt to use wget, curl, and lynx     By default, config/install.sh will attempt to use wget, curl, and
194     (in that order).  If you already know which of these programs you want     lynx (in that order).  If you already know which of these programs
195     the installer to use, then set the environment variable URLGETTER     you want the installer to use, then set the environment variable
196     to "wget", "curl", or "lynx", respectively.     URLGETTER to "wget", "curl", or "lynx", respectively.
197    
198     You can also set URLGETTER to any other command "foo" as long as     You can also set URLGETTER to any other command "foo" as long as
199     it can be invoked as     it can be invoked as
# Line 193  Line 203 
203     where <source> is the URL you want to fetch and <destination> is     where <source> is the URL you want to fetch and <destination> is
204     the file name where the result will be stored.     the file name where the result will be stored.
205    
206       2.9 Where are those "CM" directories?
207       -------------------------------------
208    
209       CM metadata (source skeletons, compiled files, stable libraries, GUIDs,
210       ...) are now stored under a directory called ".cm".  We changed this
211       from the original "CM" because of name clashes on case-insensitive
212       file systems.  However, SML/NJ itself can work with any (reasonable)
213       choice of name for the metadata directory -- but for consistency the
214       choice has to be made at installation time.
215    
216       To choose a different name for metadata directories, run
217       config/install.sh in the presence of an environment variable
218       CM_DIR_ARC.  For example, if you want to have all these directories
219       be named "FOOBAR", then run the installer (assuming a Bourne-ish
220       shell) as
221    
222          $ CM_DIR_ARC=FOOBAR config/install.sh
223    
224  3. Troubleshooting:  3. Troubleshooting:
225  -------------------  -------------------
226    
# Line 215  Line 243 
243        "xget".  You could then make a shell script that wraps xget, e.g.        "xget".  You could then make a shell script that wraps xget, e.g.
244        using a shell script "myxget" consisting of the single line:        using a shell script "myxget" consisting of the single line:
245    
246            exec xget -nv -O $2 $1           $ exec xget -nv -O $2 $1
247    
248        Once you have myxget, simply run:        Once you have myxget, simply run:
249    
250            URLGETTER=myxget config/install.sh           $ URLGETTER=myxget config/install.sh
251    
252    ----------------------------------------------------------------------------

Legend:
Removed from v.1261  
changed lines
  Added in v.1414

root@smlnj-gforge.cs.uchicago.edu
ViewVC Help
Powered by ViewVC 1.0.0