Hi!
> I think this could be adjusted to fit at the end of section 1 in the
> README file, would you be interested in proposing a patch for this ?
Sure - in fact I should probably send doc/contrib patches every time I
have to search old mails with some specific instructions :)
Something like this? I added it after the USE_OPENSSL description, which
seems to be the right place to me. Otherwise we have USE_OPENSSL in the
middle of section 1 and the information about the static build at the end.
The haproxy make line is pretty long and sets a new record in README (106
columns), but I've seen the 80 column limit is already broken by another
line anyway, so I wasn't sure if I should break the line with \ or not.
Also I did not include informations about haproxy -vv (keeping it short) and
I'm not sure if the use of a environment variable is pretty in the README.
Let me know your thoughts and I will send a full patch.
Thanks,
Lukas
diff --git a/README b/README
index 54ba1b7..9c0bca3 100644
--- a/README
+++ b/README
@@ -90,6 +90,17 @@ will automatically be linked with haproxy. Some systems also
require libz, so
if the build fails due to missing symbols such as deflateInit(), then try again
with "ADDLIB=-lz".
+To link OpenSSL statically against haproxy, build OpenSSL with the no-shared
+keyword and install it to a local directory, so your system is not affected :
+
+ $ export STATICLIBSSL=/tmp/staticlibssl
+ $ ./config --prefix=$STATICLIBSSL no-shared
+ $ make && make install_sw
+
+When building haproxy, pass that path via ADDINC and ADDLIB to make and include
+libdl ("-ldl").
+ $ make TARGET=linux2628 USE_OPENSSL=1 ADDINC=-I$STATICLIBSSL/include
ADDLIB="-L$STATICLIBSSL/lib -ldl"
+
It is also possible to include native support for ZLIB to benefit from HTTP
compression. For this, pass "USE_ZLIB=1" on the "make" command line and ensure
that zlib is present on the system.
