"SfR Fresh" - the SfR Freeware/Shareware Archive

Member "mpdist-3.7.1/INSTALL" of archive mpdist-3.7.1.tar.gz:


As a special service "SfR Fresh" has tried to format the requested source page into HTML format using source code syntax highlighting with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. That can be also achieved for any archive member file by clicking within an archive contents listing on the first character of the file(path) respectively on the according byte size field.
    1 Supported platforms
    2 ===================
    3 
    4 The mp distribution has been reported to compile and run under the following 
    5 Unix operating systems:
    6 
    7   AIX 4.1.5.
    8   Digital Unix 4.0f, cc and gcc.
    9   HP-UX 9.05/9.07 with cc
   10   IRIX 6.3.
   11   OpenBSD 2.6
   12   RedHat 5.2, 6.1
   13   Solaris 2.6, Solaris 7 and 8, cc and gcc.
   14 
   15 - An ANSI C compiler (such as gcc) is required.
   16 
   17 - To build mptool you must have the Gtk+ and GLib distributions on your
   18   computer (downloadable from www.gtk.org).
   19 
   20 
   21 Installation
   22 ============
   23 
   24    These are generic installation instructions.
   25 
   26    The `configure' shell script attempts to guess correct values for
   27 various system-dependent variables used during compilation.  It uses
   28 those values to create a `Makefile' in each directory of the package.
   29 It may also create one or more `.h' files containing system-dependent
   30 definitions.  Finally, it creates a shell script `config.status' that
   31 you can run in the future to recreate the current configuration, a file
   32 `config.cache' that saves the results of its tests to speed up
   33 reconfiguring, and a file `config.log' containing compiler output
   34 (useful mainly for debugging `configure').
   35 
   36    If you need to do unusual things to compile the package, please try
   37 to figure out how `configure' could check whether to do them, and mail
   38 diffs or instructions to the address given in the `README' so they can
   39 be considered for the next release.  If at some point `config.cache'
   40 contains results you don't want to keep, you may remove or edit it.
   41 
   42    The file `configure.in' is used to create `configure' by a program
   43 called `autoconf'.  You only need `configure.in' if you want to change
   44 it or regenerate `configure' using a newer version of `autoconf'.
   45 
   46 The simplest way to compile this package is:
   47 
   48   1. `cd' to the directory containing the package's source code and type
   49      `./configure' to configure the package for your system.  If you're
   50      using `csh' on an old version of System V, you might need to type
   51      `sh ./configure' instead to prevent `csh' from trying to execute
   52      `configure' itself.
   53 
   54      Running `configure' takes awhile.  While running, it prints some
   55      messages telling which features it is checking for.
   56 
   57   2. Type `make' to compile the package.
   58 
   59   3. Optionally, type `make check' to run any self-tests that come with
   60      the package.
   61 
   62   4. Type `make install' to install the programs and any data files and
   63      documentation.
   64 
   65   5. You can remove the program binaries and object files from the
   66      source directory by typing `make clean'.  To also remove the files
   67      that `configure' created (so you can compile the package for a
   68      different kind of computer), type `make distclean'.
   69 
   70 Compilers and Options
   71 =====================
   72 
   73    Some systems require unusual options for compilation or linking that
   74 the `configure' script does not know about.  You can give `configure'
   75 initial values for variables by setting them in the environment.  Using
   76 a Bourne-compatible shell, you can do that on the command line like
   77 this:
   78      CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
   79 
   80 Or on systems that have the `env' program, you can do it like this:
   81      env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
   82 
   83 Using a Different Build Directory
   84 =================================
   85 
   86    You can compile the package in a different directory from the one
   87 containing the source code.  Doing so allows you to compile it on more
   88 than one kind of computer at the same time.  To do this, you must use a
   89 version of `make' that supports the `VPATH' variable, such as GNU
   90 `make'.  `cd' to the directory where you want the object files and
   91 executables to go and run the `configure' script.  `configure'
   92 automatically checks for the source code in the directory that
   93 `configure' is in and in `..'.
   94 
   95 Installation Names
   96 ==================
   97 
   98    By default, `make install' will install the package's files in
   99 `/usr/local/bin', `/usr/local/man', etc.  You can specify an
  100 installation prefix other than `/usr/local' by giving `configure' the
  101 option `--prefix=PATH'.
  102 
  103    You can specify separate installation prefixes for
  104 architecture-specific files and architecture-independent files.  If you
  105 give `configure' the option `--exec-prefix=PATH', the package will use
  106 PATH as the prefix for installing programs and libraries.
  107 Documentation and other data files will still use the regular prefix.
  108 
  109    If the package supports it, you can cause programs to be installed
  110 with an extra prefix or suffix on their names by giving `configure' the
  111 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
  112 
  113 Optional Features
  114 =================
  115 
  116    Some packages pay attention to `--enable-FEATURE' options to
  117 `configure', where FEATURE indicates an optional part of the package.
  118 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
  119 is something like `gnu-as' or `x' (for the X Window System).  The
  120 `README' should mention any `--enable-' and `--with-' options that the
  121 package recognizes.
  122 
  123    For packages that use the X Window System, `configure' can usually
  124 find the X include and library files automatically, but if it doesn't,
  125 you can use the `configure' options `--x-includes=DIR' and
  126 `--x-libraries=DIR' to specify their locations.
  127 
  128 Specifying the System Type
  129 ==========================
  130 
  131    There may be some features `configure' can not figure out
  132 automatically, but needs to determine by the type of host the package
  133 will run on.  Usually `configure' can figure that out, but if it prints
  134 a message saying it can not guess the host type, give it the
  135 `--host=TYPE' option.  TYPE can either be a short name for the system
  136 type, such as `sun4', or a canonical name with three fields:
  137      CPU-COMPANY-SYSTEM
  138 
  139 See the file `config.sub' for the possible values of each field.  If
  140 `config.sub' isn't included in this package, then this package doesn't
  141 need to know the host type.
  142 
  143    If you are building compiler tools for cross-compiling, you can also
  144 use the `--target=TYPE' option to select the type of system they will
  145 produce code for and the `--build=TYPE' option to select the type of
  146 system on which you are compiling the package.
  147 
  148 Sharing Defaults
  149 ================
  150 
  151    If you want to set default values for `configure' scripts to share,
  152 you can create a site shell script called `config.site' that gives
  153 default values for variables like `CC', `cache_file', and `prefix'.
  154 `configure' looks for `PREFIX/share/config.site' if it exists, then
  155 `PREFIX/etc/config.site' if it exists.  Or, you can set the
  156 `CONFIG_SITE' environment variable to the location of the site script.
  157 A warning: not all `configure' scripts look for a site script.
  158 
  159 Operation Controls
  160 ==================
  161 
  162    `configure' recognizes the following options to control how it
  163 operates.
  164 
  165 `--cache-file=FILE'
  166      Save the results of the tests in FILE instead of `config.cache'.
  167      Set FILE to `/dev/null' to disable caching, for debugging
  168      `configure'.
  169 
  170 `--help'
  171      Print a summary of the options to `configure', and exit.
  172 
  173 `--quiet'
  174 `--silent'
  175 `-q'
  176      Do not print messages saying which checks are being made.
  177 
  178 `--srcdir=DIR'
  179      Look for the package's source code in directory DIR.  Usually
  180      `configure' can determine that directory automatically.
  181 
  182 `--version'
  183      Print the version of Autoconf used to generate the `configure'
  184      script, and exit.
  185 
  186 `configure' also accepts some other, not widely useful, options.
  187 
  188 
  189 Mp distribution specific configuration options
  190 ==============================================
  191 
  192 --disable-mptool
  193 	Do NOT build mptool
  194 
  195 --disable-mimep
  196 	Do NOT build mimep
  197 
  198 --disable-mailp
  199 	Disable the creation of the mailp link to mp
  200 
  201 --disable-newsp
  202 	Disable the creation of the newsp link to mp
  203 
  204 --disable-digestp
  205 	Disable the creation of the digestp link to mp
  206 
  207 --disable-filep
  208 	Disable the creation of the filep link to mp
  209 
  210 --disable-filofaxp
  211 	Disable the creation of the filofaxp link to mp
  212 
  213 --disable-fileofaxpp
  214 	Disable the creation of the fileofaxpp link to mp
  215 
  216 --disable-franklinp
  217 	Disable the creation of the franklinp link to mp
  218 
  219 --disable-proplanp
  220 	Disable the creation of the proplanp link to mp
  221 
  222 --disable-timemanp
  223 	Disable the creation of the timemanp link to mp
  224 
  225 --disable-timesysip
  226 	Disable the creation of the timesysip link to mp
  227 
  228 --disable-timesyspp
  229 	Disable the creation of the timesyspp link to mp
  230 
  231 --enable-bsd-print
  232 	If you use 'lpr' to print files on your system, you should use this
  233     option. By default, mp uses 'lp' to print files.
  234 
  235 --with-prologue=PATH
  236 	It is possible to change the location of the mp prologue file
  237 	with the -p command line option. It can also be defined at compile
  238 	time, by using this option and setting appropriately. If it's not 
  239     present, then a sensible default value is used.
  240 
  241 --with-gecosfields=N
  242 	Mp will extract the user's gecos field, and try to make sense of what
  243 	it finds. It applies various rules to do this. If this field is too long,
  244 	then it needs to truncate sensibly. If it's extracted N "words" or has
  245 	found a comma, then it stops extracting. If an ampersand is found, this
  246 	is expanded to the users name in capitals.
  247 	This option allows you to change the number of "words" that mp extracts
  248 	from the gecos field. By default this is 3. If needed, then it should
  249 	be uncommented, and set accordingly.
  250 
  251 --with-gecoslength=N
  252 	Mp will extract upto a certain number of characters from the user's
  253 	passwd gecos field. By default, this is 40. This option allows you to
  254 	set this to something different. If needed, then it should be uncommented,
  255 	and set accordingly.
  256 
  257 --disable-mime-support
  258 	Mimep is capable of MIME support (by using LaTeX and metamail). It uses
  259 	some functions from the mp distrubution. By default, these functions are
  260     enabled. To disable MIME support in mp, use this option.
  261 
  262 --enable-old-options
  263 	The previous version of mp had different (mainly single character)
  264 	command line options. If you'd like this version of mp/mptool to
  265 	also support those old style command line options, then you should use 
  266     this configure option.
  267 
  268 --disable-dnd
  269 	If you want to compile mptool and you don't want to include in drag and
  270     drop functionality, than you need to use this option. Mptool won't support 
  271     drag and drop but the rest of the functionality should be there.
  272 
  273 --disable-duplex
  274 	Some printers (ie. some models of HP LaserJet's) cannot handle duplex
  275 	printing. To disable this feature, use this option.