summaryrefslogtreecommitdiffstats
path: root/INSTALL.W32
diff options
context:
space:
mode:
authorAndy Polyakov <appro@openssl.org>2010-11-23 22:56:45 +0000
committerAndy Polyakov <appro@openssl.org>2010-11-23 22:56:45 +0000
commitda64e0d89877a23148c430c80a78940c4004190d (patch)
tree1fa34edbd5e2c2cc9f9a1864809ff445922db9fc /INSTALL.W32
parent88868c078601d63927afb59a8c9576769bcc1152 (diff)
INSTALL.W32: document trouble with symlinks under MSYS.
PR: 2377
Diffstat (limited to 'INSTALL.W32')
-rw-r--r--INSTALL.W329
1 files changed, 9 insertions, 0 deletions
diff --git a/INSTALL.W32 b/INSTALL.W32
index a0886b3d77..d23c4baf62 100644
--- a/INSTALL.W32
+++ b/INSTALL.W32
@@ -185,6 +185,15 @@
required. Run the installers and do whatever magic they say it takes
to start MSYS bash shell with GNU tools on its PATH.
+ N.B. Since source tar-ball can contain symbolic links, it's essential
+ that you use accompanying MSYS tar to unpack the source. It will
+ either handle them in one way or another or fail to extract them,
+ which does the trick too. Latter means that you may safely ignore all
+ "cannot create symlink" messages, as they will be "re-created" at
+ configure stage by copying corresponding files. Alternative programs
+ were observed to create empty files instead, which results in build
+ failure.
+
* Compile OpenSSL:
$ ./config