Debian Codegraph @

INSTALL

raw
1 Dependencies
2 ============
3
4 To compile a proper version of mpg321, you'll need the following
5 libraries:
6 1) mad, version 0.14.2b or better, to decode MPEG streams and ID3 tags. Get
7 it from ftp://ftp.mars.org/pub/mpeg/ .
8 2) libao, for output, from www.xiph.org. At version 0.8.0 or later is now
9 required, due to source and binary-incompatible changes. Get it from
10 http://www.xiph.org/ogg/vorbis/download/ .
11
12 mpg321-Specific Configuration
13 =============================
14
15 There are several compile-time configuration options. These can be accessed
16 from the 'configure' script:
17
18 --enable-mpg123-symlink Enable symlink of mpg123 to mpg321 [default=yes]
19
20 By default, at install time mpg321 creates a symlink from the mpg321 binary
21 to 'mpg123', allowing scripts and frontends to work seamlessly with mpg321
22 instead of mpg123. If you want this (and most people probably do), don't
23 pass any special flags to configure. If you DON'T want this, pass the flag
24 --disable-mpg123-symlink to configure.
25 (i.e., ./configure --disable-mpg123-symlink)
26
27 --with-default-audio=DA Specify default libao output plugin to use
28 [oss,sun,alsa,esd,arts]
29
30 mpg321 also allows setting a compile-time default for output. By default,
31 this just uses the libao system default, which is configurable in
32 /etc/libao.conf. But, if you'd rather mpg321 try to use a specific libao
33 output plugin, specify it with --with-default-audio=. Note that mpg321
34 can _always_ switch output plugins at runtime with the -o command-line option.
35
36 --enable-ipv6 enable IPv6 support [default: no]
37
38 mpg321 includes support for ipv6 connections in network streams if your
39 machine supports this. These are backward-compatible with ipv4 connections
40 as well, so it is usually safe to enable ipv6.
41
42 Basic Installation
43 ==================
44
45 These are generic installation instructions.
46
47 The `configure' shell script attempts to guess correct values for
48 various system-dependent variables used during compilation. It uses
49 those values to create a `Makefile' in each directory of the package.
50 It may also create one or more `.h' files containing system-dependent
51 definitions. Finally, it creates a shell script `config.status' that
52 you can run in the future to recreate the current configuration, a file
53 `config.cache' that saves the results of its tests to speed up
54 reconfiguring, and a file `config.log' containing compiler output
55 (useful mainly for debugging `configure').
56
57 If you need to do unusual things to compile the package, please try
58 to figure out how `configure' could check whether to do them, and mail
59 diffs or instructions to the address given in the `README' so they can
60 be considered for the next release. If at some point `config.cache'
61 contains results you don't want to keep, you may remove or edit it.
62
63 The file `configure.in' is used to create `configure' by a program
64 called `autoconf'. You only need `configure.in' if you want to change
65 it or regenerate `configure' using a newer version of `autoconf'.
66
67 The simplest way to compile this package is:
68
69 1. `cd' to the directory containing the package's source code and type
70 `./configure' to configure the package for your system. If you're
71 using `csh' on an old version of System V, you might need to type
72 `sh ./configure' instead to prevent `csh' from trying to execute
73 `configure' itself.
74
75 Running `configure' takes awhile. While running, it prints some
76 messages telling which features it is checking for.
77
78 2. Type `make' to compile the package.
79
80 3. Optionally, type `make check' to run any self-tests that come with
81 the package.
82
83 4. Type `make install' to install the programs and any data files and
84 documentation.
85
86 5. You can remove the program binaries and object files from the
87 source code directory by typing `make clean'. To also remove the
88 files that `configure' created (so you can compile the package for
89 a different kind of computer), type `make distclean'. There is
90 also a `make maintainer-clean' target, but that is intended mainly
91 for the package's developers. If you use it, you may have to get
92 all sorts of other programs in order to regenerate files that came
93 with the distribution.
94
95 Compilers and Options
96 =====================
97
98 Some systems require unusual options for compilation or linking that
99 the `configure' script does not know about. You can give `configure'
100 initial values for variables by setting them in the environment. Using
101 a Bourne-compatible shell, you can do that on the command line like
102 this:
103 CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
104
105 Or on systems that have the `env' program, you can do it like this:
106 env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
107
108 Compiling For Multiple Architectures
109 ====================================
110
111 You can compile the package for more than one kind of computer at the
112 same time, by placing the object files for each architecture in their
113 own directory. To do this, you must use a version of `make' that
114 supports the `VPATH' variable, such as GNU `make'. `cd' to the
115 directory where you want the object files and executables to go and run
116 the `configure' script. `configure' automatically checks for the
117 source code in the directory that `configure' is in and in `..'.
118
119 If you have to use a `make' that does not supports the `VPATH'
120 variable, you have to compile the package for one architecture at a time
121 in the source code directory. After you have installed the package for
122 one architecture, use `make distclean' before reconfiguring for another
123 architecture.
124
125 Installation Names
126 ==================
127
128 By default, `make install' will install the package's files in
129 `/usr/local/bin', `/usr/local/man', etc. You can specify an
130 installation prefix other than `/usr/local' by giving `configure' the
131 option `--prefix=PATH'.
132
133 You can specify separate installation prefixes for
134 architecture-specific files and architecture-independent files. If you
135 give `configure' the option `--exec-prefix=PATH', the package will use
136 PATH as the prefix for installing programs and libraries.
137 Documentation and other data files will still use the regular prefix.
138
139 In addition, if you use an unusual directory layout you can give
140 options like `--bindir=PATH' to specify different values for particular
141 kinds of files. Run `configure --help' for a list of the directories
142 you can set and what kinds of files go in them.
143
144 If the package supports it, you can cause programs to be installed
145 with an extra prefix or suffix on their names by giving `configure' the
146 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
147
148 Optional Features
149 =================
150
151 Some packages pay attention to `--enable-FEATURE' options to
152 `configure', where FEATURE indicates an optional part of the package.
153 They may also pay attention to `--with-PACKAGE' options, where PACKAGE
154 is something like `gnu-as' or `x' (for the X Window System). The
155 `README' should mention any `--enable-' and `--with-' options that the
156 package recognizes.
157
158 For packages that use the X Window System, `configure' can usually
159 find the X include and library files automatically, but if it doesn't,
160 you can use the `configure' options `--x-includes=DIR' and
161 `--x-libraries=DIR' to specify their locations.
162
163 Specifying the System Type
164 ==========================
165
166 There may be some features `configure' can not figure out
167 automatically, but needs to determine by the type of host the package
168 will run on. Usually `configure' can figure that out, but if it prints
169 a message saying it can not guess the host type, give it the
170 `--host=TYPE' option. TYPE can either be a short name for the system
171 type, such as `sun4', or a canonical name with three fields:
172 CPU-COMPANY-SYSTEM
173
174 See the file `config.sub' for the possible values of each field. If
175 `config.sub' isn't included in this package, then this package doesn't
176 need to know the host type.
177
178 If you are building compiler tools for cross-compiling, you can also
179 use the `--target=TYPE' option to select the type of system they will
180 produce code for and the `--build=TYPE' option to select the type of
181 system on which you are compiling the package.
182
183 Sharing Defaults
184 ================
185
186 If you want to set default values for `configure' scripts to share,
187 you can create a site shell script called `config.site' that gives
188 default values for variables like `CC', `cache_file', and `prefix'.
189 `configure' looks for `PREFIX/share/config.site' if it exists, then
190 `PREFIX/etc/config.site' if it exists. Or, you can set the
191 `CONFIG_SITE' environment variable to the location of the site script.
192 A warning: not all `configure' scripts look for a site script.
193
194 Operation Controls
195 ==================
196
197 `configure' recognizes the following options to control how it
198 operates.
199
200 `--cache-file=FILE'
201 Use and save the results of the tests in FILE instead of
202 `./config.cache'. Set FILE to `/dev/null' to disable caching, for
203 debugging `configure'.
204
205 `--help'
206 Print a summary of the options to `configure', and exit.
207
208 `--quiet'
209 `--silent'
210 `-q'
211 Do not print messages saying which checks are being made. To
212 suppress all normal output, redirect it to `/dev/null' (any error
213 messages will still be shown).
214
215 `--srcdir=DIR'
216 Look for the package's source code in directory DIR. Usually
217 `configure' can determine that directory automatically.
218
219 `--version'
220 Print the version of Autoconf used to generate the `configure'
221 script, and exit.
222
223 `configure' also accepts some other, not widely useful, options.