On Fri, Nov 15, 2002 at 11:28:04AM +0100, Richard Levitte - VMS Whacker wrote:
> In message <[EMAIL PROTECTED]> on Fri, 15 Nov 2002 11:06:21
>+0100, Corinna Vinschen <[EMAIL PROTECTED]> said:
>
> vinschen> Sorry to say that but you didn't apply them correctly. It's not
> vinschen>
> vinschen> -march=486
> vinschen>
> vinschen> but
> vinschen>
> vinschen> -march=i486.
>
> OK, fixed and committed.
>
> Sorry about that.
No worries.
I've just tested building both, 0.9.6h and 0.9.7 snapshots as of today.
No problems with 0.9.6h left. I checked also running ssh/sshd with
the new DLLs and it seems running fine.
With 0.9.7 on the other hand I had build problems, which are probably
also given in 0.9.6, just not visible in my build environment. Let me
explain from the 0.9.7 point of view.
First, there's a build problem which only affects Windows systems due
to the way DLLs are searched for. In contrast to Unixy systems, shared
libs are search in $PATH. Therefore I propose the following patch to
test/Makefile:
--- test/Makefile.ssl.orig 2002-11-15 12:20:59.000000000 +0100
+++ test/Makefile.ssl 2002-11-15 12:15:52.000000000 +0100
@@ -118,8 +118,8 @@ tests: exe apps $(TESTS)
apps:
@(cd ..; $(MAKE) DIRS=apps all)
-SET_SO_PATHS=LIBPATH="`cd ..; pwd`"; LD_LIBRARY_PATH=$$LIBPATH;
DYLD_LIBRARY_PATH=$$LIBPATH; SHLIB_PATH=$$LIBPATH; \
- export LD_LIBRARY_PATH DYLD_LIBRARY_PATH SHLIB_PATH LIBPATH
+SET_SO_PATHS=LIBPATH="`cd ..; pwd`"; LD_LIBRARY_PATH=$$LIBPATH;
+DYLD_LIBRARY_PATH=$$LIBPATH; SHLIB_PATH=$$LIBPATH; PATH="$$LIBPATH:$$PATH" \
+ export LD_LIBRARY_PATH DYLD_LIBRARY_PATH SHLIB_PATH LIBPATH PATH
alltests: \
test_des test_idea test_sha test_md4 test_md5 test_hmac \
But there's still another problem left then. Three applications die
with access violations, openssl, rc4test and bltest.
What I did then was, to build everything again. But before, I
removed my /usr/include/openssl directory which is (obviously) the
directory present from a 0.9.6 installation.
Now everything worked fine. That means, the problem here is that
gcc (JFYI, Cygwin is now on version 3.2) searches the system include
paths before searching the paths given with -I on the command line,
iff the includes are bracketed using <...> instead of "...".
I can see two possible solutions to circumvent the problem:
Either prepend -I. -I- to all other -I options like
gcc -I. -I- -I.. -I../include
according to the gcc documentation:
`-I-'
Split the include path. Any directories specified with `-I'
options before `-I-' are searched only for headers requested with
`#include "FILE"'; they are not searched for `#include <FILE>'.
If additional directories are specified with `-I' options after
the `-I-', those directories are searched for all `#include'
directives.
In addition, `-I-' inhibits the use of the directory of the current
file directory as the first search directory for `#include "FILE"'.
or change all
#include <openssl/...>
to
#include "openssl/..."
I don't see another solution, currently.
HTH,
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:vinschen@;redhat.com
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
