Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
libvmod-gcrypt
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
uplex-varnish
libvmod-gcrypt
Commits
18302333
Commit
18302333
authored
Apr 18, 2017
by
Geoff Simmons
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add docs about libgcrypt to INSTALL.rst.
parent
d924180f
Pipeline
#177
skipped
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
16 additions
and
0 deletions
+16
-0
INSTALL.rst
INSTALL.rst
+16
-0
No files found.
INSTALL.rst
View file @
18302333
...
...
@@ -11,6 +11,22 @@ resources. This sequence will install the VMOD::
>
make
check
#
to
run
unit
tests
in
src
/
tests
/*.
vtc
>
sudo
make
install
The
configure
step
requires
code
from
the
Autoconf
Archive
collection
of
m4
macros
.
If
you
encounter
difficulties
in
the
``
configure
``
step
,
make
sure
that
you
have
the
archive
installed
(
typically
as
the
package
``
autoconf
-
archive
``
on
many
distributions
).
To
configure
the
build
for
libgcrypt
,
``
configure
.
ac
``
uses
the
macro
``
AM_PATH_LIBGCRYPT
``
from
the
Autoconf
Archive
,
which
in
turn
invokes
the
``
libgcrypt
-
config
``
utility
.
The
macro
specifies
a
minimum
library
and
API
version
number
that
is
required
,
currently
libgcrypt
version
1.6.3
and
API
version
1.
If
you
want
to
build
against
a
version
of
libgcrypt
at
a
non
-
standard
location
(
that
is
,
whose
path
that
differs
from
the
one
described
by
``
libgcrypt
-
config
``),
then
use
the
``
configure
``
option
``--
with
-
libgcrypt
-
prefix
=$
LIBGCRYPT_PREFIX
``,
where
``$
LIBGCRYPT_PREFIX
``
is
the
alternative
path
.
If
you
have
installed
Varnish
in
a
non
-
standard
directory
,
call
``
autogen
.
sh
``
and
``
configure
``
with
the
``
PKG_CONFIG_PATH
``
environment
variable
pointing
to
the
appropriate
path
.
For
example
,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment