Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
TLMSP curl
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
CYBER - Cyber Security
TS 103 523 MSP
TLMSP
TLMSP curl
Commits
1f3007db
Commit
1f3007db
authored
16 years ago
by
Dan Fandrich
Browse files
Options
Downloads
Patches
Plain Diff
Document that PKG_CONFIG_PATH is the preferred way to configure with
OpenSSL.
parent
5dafa4a2
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/INSTALL
+13
-9
13 additions, 9 deletions
docs/INSTALL
with
13 additions
and
9 deletions
docs/INSTALL
+
13
−
9
View file @
1f3007db
...
...
@@ -53,8 +53,12 @@ UNIX
./configure --with-ssl
If you have OpenSSL installed somewhere else (for example, /opt/OpenSSL,)
you can run configure like this:
If you have OpenSSL installed somewhere else (for example, /opt/OpenSSL)
and you have pkg-config installed, set the pkg-config path first, like this:
env PKG_CONFIG_PATH=/opt/OpenSSL/lib/pkgconfig ./configure --with-ssl
Without pkg-config installed, use this:
./configure --with-ssl=/opt/OpenSSL
...
...
@@ -70,20 +74,20 @@ UNIX
(with the Bourne shell and its clones):
CPPFLAGS="-I/path/to/ssl/include" LDFLAGS="-L/path/to/ssl/lib" \
CPPFLAGS="-I/path/to/ssl/include" LDFLAGS="-L/path/to/ssl/lib" \
./configure
(with csh, tcsh and their clones):
env CPPFLAGS="-I/path/to/ssl/include" LDFLAGS="-L/path/to/ssl/lib" \
./configure
env CPPFLAGS="-I/path/to/ssl/include" LDFLAGS="-L/path/to/ssl/lib" \
./configure
If you have shared SSL libs installed in a directory where your run-time
linker doesn't find them (which usually causes configure failures), you can
provide the -R option to ld on some operating systems to set a hard-coded
path to the run-time linker:
LDFLAGS=-R/usr/local/ssl/lib ./configure --with-ssl
env
LDFLAGS=-R/usr/local/ssl/lib ./configure --with-ssl
MORE OPTIONS
------------
...
...
@@ -128,7 +132,7 @@ UNIX
To build with GnuTLS support instead of OpenSSL for SSL/TLS, note that
you need to use both --without-ssl and --with-gnutls.
To build with yassl support instead of OpenSSL or G
u
nTLS, you must build
To build with yassl support instead of OpenSSL or Gn
u
TLS, you must build
yassl with its OpenSSL emulation enabled and point to that directory root
with configure --with-ssl.
...
...
@@ -148,8 +152,8 @@ UNIX
The Open Watcom C compiler on Linux requires configuring with the variables:
CC=owcc AR="$WATCOM/binl/wlib" AR_FLAGS=-q
RANLIB=/bin/true
\
STRIP="$WATCOM/binl/wstrip" CFLAGS=-Wextra
./configure
CC=owcc AR="$WATCOM/binl/wlib" AR_FLAGS=-q \
RANLIB=/bin/true
STRIP="$WATCOM/binl/wstrip" CFLAGS=-Wextra
Win32
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment