summaryrefslogtreecommitdiffabout
authorSergey Poznyakoff <gray@gnu.org.ua>2017-08-05 17:26:55 (GMT)
committer Sergey Poznyakoff <gray@gnu.org.ua>2017-08-05 17:26:55 (GMT)
commitae88bd4995903a4120c6df4649e025c8bcce9383 (patch) (unidiff)
tree6dfce7613e9a7401ef0227f1a6c70c14f8de970c
parentd1fa42df66ed835305a925ae177416d99ff72d50 (diff)
downloadvmod-binlog-ae88bd4995903a4120c6df4649e025c8bcce9383.tar.gz
vmod-binlog-ae88bd4995903a4120c6df4649e025c8bcce9383.tar.bz2
Update installation instructions
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--README26
1 files changed, 17 insertions, 9 deletions
diff --git a/README b/README
index 3e271c1..b961dcd 100644
--- a/README
+++ b/README
@@ -25,25 +25,33 @@ and searching in binary log files.
25 25
26* Installation 26* Installation
27 27
28In order to compile the package you need to have Varnish source tree. 28In order to compile the package you need to have the varnishd and varnishapi
29At least Varnish 3.0.1 is required. Varnish 4.0 is OK, too. 29packages installed.
30Supposing that the varnish source tree is available under
31/usr/src/varnish-3.0.1, run:
32 30
33 ./configure --with-varnish-source=/usr/src/varnish-3.0.1 31Supposing that condition is met, run:
34 32
35The `--with-varnish-source' option is mandatory: it tells configure 33 ./configure
36where Varnish sources reside. 34
35It should be able to automatically find the necessary components. In case
36it doesn't, tweak the configuration variables as necessary. The most
37important one is PKG_CONFIG_PATH, which contains a path (in the UNIX sense)
38where the .pc files are located. It should contain a directory where the
39'varnishapi.pc' file lives. Example usage:
40
41 ./configure PKG_CONFIG_PATH=/usr/local/varnish/lib/pkgconfig:$PKG_CONFIG_PATH
42
43Please read the file INSTALL for a detailed discussion of available variables
44and command line options.
37 45
38Once configured, do 46Once configured, do
39 47
40 make 48 make
41 49
42This will build the module. After this step you can optionally run 50This will build the module. After this step you can optionally run
43'make test' to test the package. 51'make test' to test the package.
44 52
45Finally, run the following command as root: 53Finally, run the following command as root:
46 54
47 make install 55 make install
48 56
49This package contains the 'magic' file for the file(1) utility - doc/magic. 57This package contains the 'magic' file for the file(1) utility - doc/magic.

Return to:

Send suggestions and report system problems to the System administrator.