File: INSTALL

package info (click to toggle)
dqs 3.1.8-9
  • links: PTS
  • area: non-free
  • in suites: slink
  • size: 8,908 kB
  • ctags: 9,887
  • sloc: ansic: 87,447; sh: 2,952; makefile: 442; yacc: 247; lex: 94; perl: 83; csh: 51; fortran: 24; awk: 16
file content (119 lines) | stat: -rw-r--r-- 4,239 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
DQS X Installation Instructions
===============================

The following steps can be done in parallel for each architecture on
which you wish to build the DQS X distribution.

(0) IMPORTANT: Make sure that you have compiled the DQS library for
    the architecture for which you are about to build DQS X.  In other
    words, the library `<path-to-DQS>/DQS/ARCS/<architecture>/dqs.a'
    must exist.  You can determine the architecture name by running
    <path-to-DQS>/DQS/UTIL/config.guess

(1) Change directory to the top of the DQS X distribution
    e.g. `cd <path-to-DQS>/DQS/XSRC'

(2) Run the command `./Util/mkarchdir'

(3) Change directory to the architecture directory (printed in "s by
    step 2) e.g. `cd rs6000-ibm-aix3.2'

(4) Copy the generic configuration to the current directory e.g.
    `cp ../Configs/config .'

    (Note that if you've already edited a config file for another
    architecture and many of the parameters are identical, just copy
    that config file instead and make the minor changes)

(5) Edit the configuration parameters in the config file, following
    the directions therein

(6) If your system does indeed have xmkmf and imake (programs which
    are usually part of the X11 distribution) then go to step 8

(7) (I.e. you DO NOT have xmkmf and imake)

    Copy the generic "no imake" configuration to the current directory
    e.g. `cp ../Configs/config.noimake .'

    (Note that if you've already edited a config.noimake file for
    another architecture and many of the parameters are identical,
    just copy that config.noimake file instead and make the minor
    changes)

    Edit the configuration parameters in the config.noimake file,
    following the directions therein

    Run the command `../Util/mkarch.noimake'

    (You can go build the software for other architectures, if
    desired, returning to finish this particular installation after
    compilation is finished)

    Go to step 9

(8) (I.e. you DO have xmkmf and imake)

    Run the command `../Util/mkarch'

    (You can go build the software for other architectures, if
    desired, returning to finish this particular installation after
    compilation is finished)

(9) Run the command `make install'

(10) The Adobe font metrics files (*.afm) are not installed
     automatically, as they may already exist on some systems.  
     Create the AFM directory that you specified (AFMPATH) in the
     configuration file, then copy all of the AFM files 
     (i.e. XSRC/qusage/plotter-6.0pl7/afm/*) into the AFM directory.
     This is necessary in order to use qusage's PostScript output
     capability.

(11) If desired, edit the X application defaults files AQmon and
     Qusage that were installed in the XAPPDEFDIR directory.

(12) Enjoy!

Potential Installation Problems and Possible Solutions
------------------------------------------------------

Problem: installation is unsuccessful.
Solution: Don't send me email saying "it doesn't work".  Check the
  following Problem/Solution pairs and see if any apply.  If not, I'd
  appreciate a coherent bug report.
  Include the following:
     Version number of the distribution
     If it's an installation problem,
       output from the `make'
     else If it's a run-time problem,
       the buggy output, if available
     A description of the problem

Problem: Failure to compile a C source file.
Solution: Note that some compilers will complain a lot (give warnings)
  but still succeed.  Otherwise...
  Try another compiler, if available e.g. GNU cc (gcc).
  Include output from the compilation in a bug report.

Problem: xmkmf or imake doesn't work properly.
Solution: I've seen an imake that inserted a long string of NUL
  characters at the end of the Makefile it produced.  Also seen
  imake's that put the XCOMMs in the Makefile, on which make
  subsequently chokes.

  I suggest trying the non-imake installation instructions.  If your
  xmkmf/imake has successfully installed most other packages, let me
  hear about it.

Problem: awk isn't available on my system.
Solution: Install GNU awk (gawk).  Available at popular anonymous FTP
  sites.

-----
Kingsley Kerce (kerce@scri.fsu.edu)
-----
GNU Emacs
Local Variables:
mode: text
End: