I rsync'd and pulled OpenSSL_1_0_1-stable today. With the strtoull() fix
and this patch
.......
--- apps/apps.c.old 2011-12-12 11:02:32.593185016 -0800
+++ apps/apps.c 2012-01-05 22:31:30.011105020 -0800
@@ -109,7 +109,7 @@
*
*/
-#ifndef _POSIX_C_SOURCE
+#if !defined(_POSIX_C_SOURCE) && defined(OPENSSL_SYS_VMS)
#define _POSIX_C_SOURCE 2 /* On VMS, you need to define this to get
the declaration of fileno(). The value
2 is to make sure no function defined
--- crypto/ui/ui_openssl.c.old 2009-10-04 09:43:21.000000000 -0700
+++ crypto/ui/ui_openssl.c 2012-01-05 22:31:53.221105005 -0800
@@ -122,7 +122,7 @@
* sigaction and fileno included. -pedantic would be more appropriate for
* the intended purposes, but we can't prevent users from adding -ansi.
*/
-#ifndef _POSIX_C_SOURCE
+#if !defined(_POSIX_C_SOURCE) && defined(OPENSSL_SYS_VMS)
#define _POSIX_C_SOURCE 2
#endif
#include <signal.h>
.......
to deal with _POSIX_C_SOURCE issues OpenSSL builds on OpenServer 5.0.7
CONFIGURE_ARGS=sco5-gcc zlib no-sse2
Unfortunately one of the tests core dumps.
Here is what gdb says.
.......
$ gdb -c core ./ssltest
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i586-pc-sco3.2v5.0"...
Core was generated by `ssltest'.
Program terminated with signal 4, Illegal instruction.
Reading symbols from /usr/lib/libsocket.so.2...done.
Loaded symbols for /usr/lib/libsocket.so.2
Reading symbols from /usr/lib/libnsl.so...done.
Loaded symbols for /usr/lib/libnsl.so
Reading symbols from /usr/lib/libz.so.1...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /usr/lib/libc.so.1...done.
Loaded symbols for /usr/lib/libc.so.1
#0 0x080d8590 in gcm_ghash_4bit_mmx ()
(gdb) bt
#0 0x080d8590 in gcm_ghash_4bit_mmx ()
#1 0x30201000 in ?? ()
Cannot access memory at address 0xe
(gdb)
.......
Unfortunatly that's about all I knwow to do with gdb.
--
Tim Rice Multitalents (707) 456-1146
[email protected] (707) 887-1469
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
