Re: OpenSSL 0.9.8 Beta 1
In message [EMAIL PROTECTED] on Sat, 21 May 2005 19:21:20 -0700 (PDT), Tim Rice [EMAIL PROTECTED] said: tim On Fri, 20 May 2005, Richard Levitte - VMS Whacker wrote: tim tim In message [EMAIL PROTECTED] on Thu, 19 May 2005 22:14:20 -0700 (PDT), Tim Rice [EMAIL PROTECTED] said: tim tim Hmm... I personally do not support SCO products for political tim reasons, so I'm not going to offer much about them. However, tim it looks like the CC and CFLAGS variables do not follow along tim in the build for some of your platforms, and that has me a bit tim worried. I'll look at it today or tomorrow... tim tim If you have access to a Solaris 8 box you can see the problem tim there. GNU make works and the system make does not. tim The CHANGES file did not mention requiring GNU make now. tim Has this changed for 0.9.8 or is it a bug in the Makefile? It's a bug in the Makefile. Try a later 0.9.8 snapshot and check if it makes a difference, or try the beta that I'm gong to release tomorrow. Cheers, Richard - Please consider sponsoring my work on free software. See http://www.free.lp.se/sponsoring.html for details. -- Richard Levitte [EMAIL PROTECTED] http://richard.levitte.org/ When I became a man I put away childish things, including the fear of childishness and the desire to be very grown up. -- C.S. Lewis __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
Re: OpenSSL 0.9.8 Beta 1
tim Hmm... I personally do not support SCO products for political tim reasons, so I'm not going to offer much about them. However, tim it looks like the CC and CFLAGS variables do not follow along tim in the build for some of your platforms, and that has me a bit tim worried. I'll look at it today or tomorrow... tim tim If you have access to a Solaris 8 box you can see the problem tim there. GNU make works and the system make does not. tim The CHANGES file did not mention requiring GNU make now. tim Has this changed for 0.9.8 or is it a bug in the Makefile? It's a bug in the Makefile. Try a later 0.9.8 snapshot and check if it makes a difference, or try the beta that I'm gong to release tomorrow. There are couple of edges remaining, which I work on and fix today. A. __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
Re: [ANNOUNCE] OpenSSL 0.9.8 beta 1 released
Hi Andy, On May 21 22:36, Andy Polyakov wrote: Speaking of documentation:-) Is cygwin memory layout documented somewhere? What I'm trying to ask is if you can provide a pointer. If it's documented in commentary section in source code, then could you be so kind to give some approximate directions where to look? A. It's not exactly documented, no. If you download the sources, there's a file how-cygheap-works.txt, which explains the basics about cygwin's own heap which is inherited to child applications on fork and exec. Other than that, there are just a couple of shared memory areas for various puposes (process list, tape driver, etc) and the Cygwin DLL itself. The DLL is loaded to 0x6100, the cygheap is always expected to be right after the end of the DLL's loading area. The shared memory regions have been accidentally loaded to 0x0400 since 1.5.13 up to current 1.5.16, but will reside beginning at 0x6000 with the upcoming 1.5.17. If you need more details, you will have to look into the sources, I assume. If you have questions, feel free to send PM, I think more of that is pretty OT for this list. Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat, Inc. __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
Problems with engines in 0.9.8-beta1
Hi, now that I had first contact with engines, I thought it might be better to give them some testing. It turns out that loading the engines works fine, but there are three engines which don't work, and it seems to me that this isn't a Cygwin specific problem. These three engines don't load: lib4758_cca.so libgmp.so libncipher.so One of them is not a mystery. libgmp.so is just empty, because OPENSSL_USE_GMP wasn't set when building. So that can be ignored. However, I found that lib4758_cca.so and libncipher.so don't load, because the engine id differs from the engine name. The engine id of lib4758_cca.so is 4758cca instead of 4758_cca, the id of libncipher.so is chil instead of ncipher. The result is this. If I try, for instance, to open the engine ncipher with openssl: OpenSSL engine ncipher 1608:error:260B606D:engine routines:DYNAMIC_LOAD:init failed:eng_dyn.c:521: 1608:error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:411:id=ncipher This is because the loaded bind function bind_fn() rejects being initialized, because the incoming id ncipher is not equal the engine's own id engine_hwcrhk_id == chil. OTOH, when trying to load an engine chil, this happens: OpenSSL engine chil 3668:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:162:filename(/usr/lib/engines/libchil.so): dlopen, Win32 error 126 3668:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:244: 3668:error:260B6084:engine routines:DYNAMIC_LOAD:dso not found:eng_dyn.c:450: 3668:error:2606A074:engine routines:ENGINE_by_id:no such engine:eng_list.c:411:id=chil It tries to open an engine called libchil.so, which isn't present. The problem is equivalent for lib4758_cca.so. So it seems, either the engine ids are just wrong and should be changed, or the names of the created shared libs is wrong and should be changed. Corinna -- Corinna Vinschen Cygwin Project Co-Leader Red Hat, Inc. __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
Re: OpenSSL 0.9.8 Beta 1
On Fri, 20 May 2005, Andy Polyakov wrote: make[1]: Entering directory `/usr/local/src/libs/openssl-0.9.8/crypto' gcc -I. -I.. -I../include -fPIC -DOPENSSL_PIC -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -mcpu=pentium -DL_ENDIAN -DTERMIO -O3 -fomit-frame-pointer -Wall -DOPENSSL_BN_ASM_PART_WORDS -DOPENSSL_IA32_SSE2 -DSHA1_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM -c -o x86cpuid-elf.o x86cpuid-elf.s x86cpuid-elf.s: Assembler messages: x86cpuid-elf.s:144: Error: suffix or operands invalid for `pxor' ./config no-sse2. It might be good idea to have ./config add it automatically for some platforms... Starting with Solaris x86 prior 5.10 and bsdi... And all unixware-* targets, and all sco3-* and sco5-* targets. Even with no-sse2 on unixware-7 I get ... $ make making all in crypto... cc -I. -I.. -I../include -Kpic -DOPENSSL_PIC -DOPENSSL_THREADS -Kthread -DDSO_DLFCN -DHAVE_DLFCN_H -O -DFILIO_H -Kalloca -DOPENSSL_BN_ASM_PART_WORDS -DS HA1_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM -c -o x86cpuid-elf.o x86cpuid-elf.s UX:as: ERROR: x86cpuid-elf.s:173:syntax error at name: f UX:as: ERROR: x86cpuid-elf.s:175:syntax error at integer constant: 1 *** Error code 1 (bu21) ... Solaris 8 Configured for solaris-sparcv9-gcc. Waiting for build to finish Sending output to nohup.out [EMAIL PROTECTED] 60% make making all in crypto... ar r ../libcrypto.a cryptlib.o mem.o mem_clr.o mem_dbg.o cversion.o ex_data.o tmdiff.o cpt_err.o ebcdic.o uid.o o_time.o o_str.o o_dir.o /usr/ccs/bin/ranlib ../libcrypto.a || echo Never mind. making all in crypto/objects... cc -I.. -I../.. -I../../include -g -c o_names.c sh: cc: not found *** Error code 1 make: Fatal error: Command failed for target `o_names.o' Current working directory /usr/local/src/libs/openssl-0.9.8/crypto/objects *** Error code 1 This was a problem with /usr/ccs/bin/make, but it was fixed just prior 0.9.8-beta1 cut. And I can't reproduce it now, not with /usr/ccs/bin/make nor GNU make... What does current working directory ... 0.9.8/ mean? That's it's not actually -beta1 tarball? If not, how old is it then? A. Things are working much better today. I'm actually working from my rsync'd CVS using the OpenSSL_0_9_8-stable tag. -- Tim RiceMultitalents(707) 887-1469 [EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
