Hi Andy,
Am 19.11.2010 01:55, schrieb Guenter via RT:
> Am 18.11.2010 23:58, schrieb Andy Polyakov via RT:
>> Could you examine ticket #2273. Can you confirm that it's same issue
>> discussed at the very end? A.
> argh! Now remember we discussed this issue already with last release ...
> will asap repack the release archive on Linux and check if that does any
> better ...
yes - that's same issue; I did delete my source tree, and extracted from
MSYS with:
tar xfhz openssl-1.0.0b.tar.gz
then patched with RT #2374 (thanks Steve for committing!), and
compilation went to end including test binaries.
If we cant get this issue fixed with release tarballs I'd suggest that
we at least just *now* add this important hint to INSTALL.W32:
--- INSTALL.W32.orig 2010-07-09 14:31:41 +0000
+++ INSTALL.W32 2010-11-19 05:31:26 +0000
@@ -184,6 +184,9 @@
MinGW and MSYS are available from http://www.mingw.org/, both are
required. Run the installers and do whatever magic they say it takes
to start MSYS bash shell with GNU tools on its PATH.
+ Since the release tarballs contain symlinks which MSYS cant deal with
+ you must use tar with the -h option to dereference the symlinks:
+ tar xfhz openssl-x.y.zr.tar.gz
* Compile OpenSSL:
that might probably avoid some more RTs in future ...
I did also test mingw32-cross on a SuSE 11.1 box, and that went fine too
(with symlinks) after patched with RT #2374.
thanks, Günter.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
