From: Daniel Stenberg <daniel@haxx.se>
Date: Tue, 26 Oct 2004 08:09:16 +0000 (+0000)
Subject: mention how LDFLAGS=-R can be used (or LD_LIBRARY_PATH or ld.so.conf)
X-Git-Tag: curl-7_12_3~266
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=2a80a4c5210b10f84f97686583b5bc8e1511cfd1;p=thirdparty%2Fcurl.git

mention how LDFLAGS=-R can be used (or LD_LIBRARY_PATH or ld.so.conf)
---

diff --git a/docs/INSTALL b/docs/INSTALL
index 7b452cedb0..1d6386089c 100644
--- a/docs/INSTALL
+++ b/docs/INSTALL
@@ -79,8 +79,18 @@ UNIX
        env CPPFLAGS="-I/path/to/ssl/include" LDFLAGS="-L/path/to/ssl/lib" \
        ./configure
 
-   If your SSL library was compiled with rsaref (usually for use in the United
-   States), you may also need to set:
+   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
+
+   Another option to the previous trick, is to set LD_LIBRARY_PATH or edit the
+   /etc/ld.so.conf file.
+
+   If your SSL library was compiled with rsaref (this was common in the past
+   when used in the United States), you may also need to set:
 
      LIBS=-lRSAglue -lrsaref
      (as suggested by Doug Kaufman)