Re: DJGPP patch for 0.9.7-stable

[Richard Levitte - VMS Whacker]

In message <[EMAIL PROTECTED]> on Sat, 11 Jan 
2003 23:49:28 -0800 (PST), Doug Kaufman <[EMAIL PROTECTED]> said:

dkaufman> I noticed that the makefile contains a special line for
dkaufman> DJGPP, similar to the one for Cygwin. This isn't needed for
dkaufman> DJGPP. Patch attached.

Please explain why .dll loading would be different in that particular
case...

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken  \ S-168 35  BROMMA  \ T: +46-8-26 52 47
\  SWEDEN   \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/

Unsolicited commercial email is subject to an archival fee of $400.
See  for more info.

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

[openssl.org #452] OpenSSL error

[Jimmy Cheng Sze Ngee via RT]

Hi,
I had a problem when installing SSL @ SUN Solaris 8
Please advise , thanks.

regards, 
Jimmy

Error message:
***
gcc -I.. -I../.. -I../../include -DOPENSSL_SYSNAME_ULTRASPARC
-DOPENSSL_THREADS -D_RE
ENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -m32 -mcpu=ultrasparc
-O3 -fomit
-frame-pointer -Wall -DB_ENDIAN -DBN_DIV2W -DMD5_ASM  -c  rmd_one.c
ar  r ../../libcrypto.a rmd_dgst.o rmd_one.o
/usr/ccs/bin/ranlib ../../libcrypto.a || echo Never mind.
making all in crypto/des...
gcc -I.. -I../.. -I../../include -DOPENSSL_SYSNAME_ULTRASPARC
-DOPENSSL_THREADS -D_RE
ENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -m32 -mcpu=ultrasparc
-O3 -fomit
-frame-pointer -Wall -DB_ENDIAN -DBN_DIV2W -DMD5_ASM  -c  set_key.c
In file included from des_locl.h:80,
 from set_key.c:66:
/usr/local/lib/gcc-lib/sparc-sun-solaris2.8/2.95.3/include/math.h:5: math.h:
No such
file or directory
*** Error code 1
make: Fatal error: Command failed for target `set_key.o'
Current working directory /opt/tmp/openssl-0.9.7/crypto/des
*** Error code 1
make: Fatal error: Command failed for target `subdirs'
Current working directory /opt/tmp/openssl-0.9.7/crypto
make: *** [sub_all] Error 1


__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: DJGPP patch for 0.9.7-stable

[Andy Polyakov]

> dkaufman> I noticed that the makefile contains a special line for
> dkaufman> DJGPP, similar to the one for Cygwin. This isn't needed for
> dkaufman> DJGPP. Patch attached.
> 
> Please explain why .dll loading would be different in that particular
> case...

Because loading of Windows .dll is not an option in DJGPP? Isn't DJGPP
so to say all own OS? At least it doesn't rely upon WIN32 API, but
MS-DOS "int 21h" and *if* it supports some kind of dynamicaly loadable
objects, it has nothing to do with Windows LoadLibrary call, the one
using %PATH% to look for .dlls. A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

[Andy Polyakov]

> > This is a preliminary patch and I need to think it through before I
> > commit it. Maybe we should solve it in some other way (like with ELF).
> > Any DJGPP out there who care to verify if this doesn't break DJGPP?
> 
> I tried this patch on DJGPP both as normally compiled and also using
> the asm modules (put ${x86_out_asm} in the DJGPP config-string
  ^^^ Oh! I missed that. I mean the fact that they are not
actually engaged in the default configuration. Any particular reason
why?

> No problems with compilation or testing.

Great! As for "preliminarity" of the patch. I've chosen to just promote
it to "final" and throw it in and not do something similar to ELF
solution. Basically because of lack of motivation:-) Cheers. A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [openssl.org #451] SX6 port

[Andy Polyakov via RT]

> + "sx6", "cc:-g -DTERMIOS::(unknown):::SIXTY_FOUR_BIT DES_INT:::",

No optimization? Not even lousy -O?

SIXTY_FOUR_BIT? SIXTY_FOUR_BIT aims ILP32 ABIs implemented on 64-bit
CPUs, N32 ABI on IRIX 6 is one example. If your sizeof(long)==8, then
you should use SIXTY_FOUR_BIT_LONG. Please confirm.

A.

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

openssl 0.9.7, bug in ui_lib.c:general_allocate_string

[Jacques A. Vidrine]

Hello,

Regarding openssl 0.9.7:

When using OPENSSL_DES_LIBDES_COMPATIBILITY, I noticed that
`des_read_pw_string' was not functioning.  I tracked this down to a
bug in crypto/ui/ui_lib.c:general_allocate_string().

Callers of general_allocate_string (including ultimately
UI_UTIL_read_pw, which is used to implement des_read_pw_string) expect
it to return 0 for success, or non-zero for failure.  However, the
return code is mishandled here:

164 static int general_allocate_string(UI *ui, const char *prompt,
 [...]
168 int ret = -1;
 [...]
179 ret=sk_UI_STRING_push(ui->strings, s);
180 /* sk_push() returns 0 on error.  Let's addapt that */
181 if (ret <= 0) ret--;

sk_UI_STRING_push returns 0 on error, or a positive integer
for success.  Therefore, if sk_UI_STRING_push succeeds,
general_allocate_string returns a positive integer, which does not
match what callers expect.

This is the simple fix I applied locally (note the same issue exists
in general_allocate_boolean).

--- ui_lib.cWed Dec  4 18:04:40 2002
+++ ui_lib.cSun Jan 12 09:04:16 2003
@@ -178,7 +178,7 @@
s->_.string_data.test_buf=test_buf;
ret=sk_UI_STRING_push(ui->strings, s);
/* sk_push() returns 0 on error.  Let's addapt that */
-   if (ret <= 0) ret--;
+   ret = (ret == 0) ? -1 : 0;
}
else
free_string(s);
@@ -228,7 +228,7 @@
ret=sk_UI_STRING_push(ui->strings, s);
/* sk_push() returns 0 on error.
   Let's addapt that */
-   if (ret <= 0) ret--;
+   ret = (ret == 0) ? -1 : 0;
}
else
free_string(s);


Cheers,
-- 
Jacques A. Vidrine <[EMAIL PROTECTED]>  http://www.celabo.org/
NTT/Verio SME  . FreeBSD UNIX .   Heimdal Kerberos
[EMAIL PROTECTED] .  [EMAIL PROTECTED]  .  [EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: DJGPP patch for 0.9.7-stable

[Doug Kaufman]

On Sun, 12 Jan 2003, Andy Polyakov wrote:

> > dkaufman> I noticed that the makefile contains a special line for
> > dkaufman> DJGPP, similar to the one for Cygwin. This isn't needed for
> > dkaufman> DJGPP. Patch attached.
> > 
> > Please explain why .dll loading would be different in that particular
> > case...
> 
> Because loading of Windows .dll is not an option in DJGPP? Isn't DJGPP
> so to say all own OS? At least it doesn't rely upon WIN32 API, but
> MS-DOS "int 21h" and *if* it supports some kind of dynamicaly loadable
> objects, it has nothing to do with Windows LoadLibrary call, the one
> using %PATH% to look for .dlls. A.

To clarify, DJGPP runs in a true DOS environment rather than a Windows
environment. Multitasking is not supported. It does not support
dynamically loaded libraries at all. DJGPP binaries can run in a DOS
box under Windows, but run as DOS rather than native Windows programs.
  Doug
-- 
Doug Kaufman
Internet: [EMAIL PROTECTED]

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

[Doug Kaufman]

On Sun, 12 Jan 2003, Andy Polyakov wrote:

> > I tried this patch on DJGPP both as normally compiled and also using
> > the asm modules (put ${x86_out_asm} in the DJGPP config-string
>   ^^^ Oh! I missed that. I mean the fact that they are not
> actually engaged in the default configuration. Any particular reason
> why?

The only reason is to maintain 386 compatibility. The last time I
asked (I think it was about a year ago), there was a question as to
whether 386 incompatible instructions were used in the asm files, even
if "386" was specified in the Configure options. DJGPP programs should
be able to work on the 386 architecture. I don't have a 386 machine
to test with. I have no objection to using the asm files as long as
doing so doesn't break 386 compatibility. If the 386 compatibility
problem is real, perhaps instructions for changing the config-string
in Configure should be put in INSTALL.DJGPP, for those wishing to use
the asm files. I am not a programmer and don't know how to check for
assembler instructions incompatible with the 386 myself.
 Doug
-- 
Doug Kaufman
Internet: [EMAIL PROTECTED]

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

[Andy Polyakov]

> > > I tried this patch on DJGPP both as normally compiled and also using
> > > the asm modules (put ${x86_out_asm} in the DJGPP config-string
> >   ^^^ Oh! I missed that. I mean the fact that they are not
> > actually engaged in the default configuration. Any particular reason
> > why?
> 
> The only reason is to maintain 386 compatibility. The last time I
> asked (I think it was about a year ago), there was a question as to
> whether 386 incompatible instructions were used in the asm files, even
> if "386" was specified in the Configure options.

If you './Configure ... DJGPP 386', then pure 386 asm code will be
generated. Well, it's all about single instruction, bswapl to be
specific... A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

[openssl.org #453] Re: DJGPP patch for 0.9.7-stable

[[EMAIL PROTECTED] via RT]

On Sun, 12 Jan 2003, Andy Polyakov wrote:

> > dkaufman> I noticed that the makefile contains a special line for
> > dkaufman> DJGPP, similar to the one for Cygwin. This isn't needed for
> > dkaufman> DJGPP. Patch attached.
> > 
> > Please explain why .dll loading would be different in that particular
> > case...
> 
> Because loading of Windows .dll is not an option in DJGPP? Isn't DJGPP
> so to say all own OS? At least it doesn't rely upon WIN32 API, but
> MS-DOS "int 21h" and *if* it supports some kind of dynamicaly loadable
> objects, it has nothing to do with Windows LoadLibrary call, the one
> using %PATH% to look for .dlls. A.

To clarify, DJGPP runs in a true DOS environment rather than a Windows
environment. Multitasking is not supported. It does not support
dynamically loaded libraries at all. DJGPP binaries can run in a DOS
box under Windows, but run as DOS rather than native Windows programs.
  Doug
-- 
Doug Kaufman
Internet: [EMAIL PROTECTED]

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

[openssl.org #454] [PATCH] FreeBSD openssl-0.9.7

[(Dirk Meyer) via RT]

Hi,

In order to support compilation on FreeBSD I have to suggest some patches.
Please revise  and send me comment.

regesssion test looks fine for:
http://people.freebsd.org/~dinoex/ports/openssl097.i386.stable
http://people.freebsd.org/~dinoex/ports/openssl097.i386.current
http://people.freebsd.org/~dinoex/ports/openssl097.alpha.current
http://people.freebsd.org/~dinoex/ports/openssl097.sparc64.current
http://people.freebsd.org/~dinoex/ports/openssl097.ia64.current

Gruß Dirk

- Dirk Meyer, Im Grund 4, 34317 Habichtswald, Tel 05606/6512 Q (voice)
- Origin: DINOEX Habichtswald  -FRG-  [[EMAIL PROTECTED]]
- [[EMAIL PROTECTED]],[[EMAIL PROTECTED]],[[EMAIL PROTECTED]]

--- Makefile.org.orig   Thu Apr  5 13:08:02 2001
+++ Makefile.orgSat Oct 12 22:10:18 2002
@@ -250,6 +250,21 @@
done
 
 build-shared: clean-shared do_$(SHLIB_TARGET) link-shared
+
+freebsd-shared:
+   for i in ${SHLIBDIRS}; do \
+   rm -f lib$$i.a lib$$i.so \
+   lib$$i.so.${SHLIBVER}; \
+   ${MAKE} CC='${CC}' PLATFORM='${PLATFORM}' CFLAG='-fPIC ${CFLAG}' 
+SDIRS='${SDIRS}' INSTALLTOP='${INSTALLTOP}' PEX_LIBS='${PEX_LIBS}' 
+EX_LIBS='${EX_LIBS}' BN_ASM='${BN_ASM}' DES_ENC='${DES_ENC}' BF_ENC='${BF_ENC}' 
+CAST_ENC='${CAST_ENC}' RC4_ENC='${RC4_ENC}' RC5_ENC='${RC5_ENC}' 
+SHA1_ASM_OBJ='${SHA1_ASM_OBJ}' MD5_ASM_OBJ='${MD5_ASM_OBJ}' 
+RMD160_ASM_OBJ='${RMD160_ASM_OBJ}' AR='${AR}' DIRS=$$i clean all || exit 1; \
+   ( set -x; ${CC}  -nodefaultlibs -shared -o lib$$i.so.${SHLIBVER} \
+   -Wl,-S,-soname=lib$$i.so.${SHLIBVER} \
+   -Wl,${WHOLE_ARCHIVE_FLAG} lib$$i.a ) || exit 1; \
+   rm -f lib$$i.a; (cd $$i ; ${MAKE} clean) || exit 1 ;\
+   done;
+   @set -x; \
+   for i in ${SHLIBDIRS}; do \
+   ln -s lib$$i.so.${SHLIBVER} lib$$i.so; \
+   done;
 
 do_bsd-gcc-shared: do_gnu-shared
 do_linux-shared: do_gnu-shared
--- Configure.orig  Fri Dec 27 17:35:11 2002
+++ Configure   Sat Jan 11 01:44:38 2003
@@ -350,7 +350,9 @@
 #
 # This probably belongs in a different section.
 #
-"FreeBSD-alpha","gcc:-DTERMIOS -O 
-fomit-frame-pointer::(unknown):::SIXTY_FOUR_BIT_LONG RC4_CHUNK DES_INT DES_PTR 
DES_RISC2::dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
+"FreeBSD-alpha","$ENV{CC}:-DTERMIOS $ENV{CFLAGS}::(unknown):::SIXTY_FOUR_BIT_LONG 
+RC4_CHUNK DES_INT DES_PTR 
+DES_RISC2::dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
+"FreeBSD-sparc64","$ENV{CC}:-DTERMIOS -DB_ENDIAN -DULTRASPARC -DBN_DIV2W 
+$ENV{CFLAGS}::(unknown):::SIXTY_FOUR_BIT_LONG RC4_CHAR RC4_CHUNK DES_INT DES_PTR 
+DES_RISC1 DES_UNROLL 
+BF_PTR::dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
+"FreeBSD-ia64","$ENV{CC}:-DL_ENDIAN -DTERMIOS 
+$ENV{CFLAGS}::(unknown):::SIXTY_FOUR_BIT_LONG RC4_CHUNK 
+RC4_CHAR:asm/ia64-cpp.o:dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
 
  Alpha Linux with GNU C and Compaq C setups
 # Special notes:
@@ -395,8 +397,8 @@
 "NetBSD-sparc","gcc:-DTERMIOS -O3 -fomit-frame-pointer -mv8 -Wall 
-DB_ENDIAN::(unknown):::BN_LLONG MD2_CHAR RC4_INDEX 
DES_UNROLL::dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
 "NetBSD-m68",  "gcc:-DTERMIOS -O3 -fomit-frame-pointer -Wall 
-DB_ENDIAN::(unknown):::BN_LLONG MD2_CHAR RC4_INDEX 
DES_UNROLL::dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
 "NetBSD-x86",  "gcc:-DTERMIOS -O3 -fomit-frame-pointer -m486 
-Wall::(unknown):::BN_LLONG ${x86_gcc_des} 
${x86_gcc_opts}::dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
-"FreeBSD-elf",  "gcc:-DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O3 -m486 
-Wall::-pthread -D_REENTRANT -D_THREAD_SAFE -D_THREADSAFE:::BN_LLONG ${x86_gcc_des} 
${x86_gcc_opts}:${x86_elf_asm}:dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
-"FreeBSD",  "gcc:-DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O3 -m486 
-Wall::(unknown):::BN_LLONG ${x86_gcc_des} ${x86_gcc_opts}:${x86_out_asm}",
+"FreeBSD-elf",  "$ENV{CC}:-DTERMIOS -DL_ENDIAN $ENV{CFLAGS} -Wall::-pthread 
+-D_REENTRANT -D_THREAD_SAFE -D_THREADSAFE:::BN_LLONG ${x86_gcc_des} 
+${x86_gcc_opts}:${x86_elf_asm}:dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
+"FreeBSD",  "$ENV{CC}:-DTERMIOS -DL_ENDIAN $ENV{CFLAGS} 
+-Wall::(unknown):::BN_LLONG ${x86_gcc_des} ${x86_gcc_opts}:${x86_out_asm}",
 "bsdi-gcc", "gcc:-O3 -ffast-math -DL_ENDIAN -DPERL5 -m486::(unknown):::RSA_LLONG 
${x86_gcc_des} ${x86_gcc_opts}:${x86_bsdi_asm}",
 "bsdi-elf-gcc", "gcc:-DPERL5 -DL_ENDIAN -fomit-frame-pointer -O3 -m486 
-Wall::(unknown)::-ldl:BN_LLONG ${x86_gcc_des} 
${x86_gcc_opts}:${x86_elf_asm}:dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
 "nextstep","cc:-O -Wall::(unknown):::BN_LLONG ${x86_gcc_des} 
${x86_gcc_opts}:::",
--- config.orig Fri Dec  6 08:45:11 2002
+++ config  Sat Jan 11 01:37:40 2003
@@ -206,6 +206,8 @@
Pentium\ II

[openssl.org #455] [BUG] FreeBSD openssl-0.9.7 I386_ONLY

[(Dirk Meyer) via RT]

while compiling on a 486 cpu:
# gcc --version
2.7.2.1

- 0.9.6 seems to work fine ...
- config called  i396
- #define I386_ONLY is set in opensslconf.h

(cd asm; /usr/local/bin/perl des-586.pl cpp >dx86unix.cpp)
gcc -E -DOUT asm/dx86unix.cpp | as -o asm/dx86-out.o
des-586.s: Assembler messages:
des-586.s:2458: Error: Unimplemented segment type 0 in parse_operand
des-586.s:2645: Error: Unimplemented segment type 0 in parse_operand
*** Error code 1

Stop.

kind regards Dirk

- Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany
- [[EMAIL PROTECTED]],[[EMAIL PROTECTED]],[[EMAIL PROTECTED]]

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: DJGPP patch for 0.9.7-stable

[Richard Levitte - VMS Whacker]

In message <[EMAIL PROTECTED]> on Sun, 12 Jan 2003 14:12:24 +0100, Andy 
Polyakov <[EMAIL PROTECTED]> said:

appro> > dkaufman> I noticed that the makefile contains a special line for
appro> > dkaufman> DJGPP, similar to the one for Cygwin. This isn't needed for
appro> > dkaufman> DJGPP. Patch attached.
appro> > 
appro> > Please explain why .dll loading would be different in that particular
appro> > case...
appro> 
appro> Because loading of Windows .dll is not an option in DJGPP? Isn't DJGPP
appro> so to say all own OS? At least it doesn't rely upon WIN32 API, but
appro> MS-DOS "int 21h" and *if* it supports some kind of dynamicaly loadable
appro> objects, it has nothing to do with Windows LoadLibrary call, the one
appro> using %PATH% to look for .dlls. A.

Ah.  Then why did we litter the Makefiles with tests of DJGPP, and why
whould only the one Doug mentioned be removed?

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken  \ S-168 35  BROMMA  \ T: +46-8-26 52 47
\  SWEDEN   \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/

Unsolicited commercial email is subject to an archival fee of $400.
See  for more info.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [CVS] OpenSSL: OpenSSL_0_9_7-stable: openssl/ ConfigureMakefile.org o...

[Richard Levitte - VMS Whacker]

In message <[EMAIL PROTECTED]> on Sun, 12 Jan 2003 
17:35:31 +0100 (CET), "Andy Polyakov" <[EMAIL PROTECTED]> said:

appro>   Log:
appro> IA-32 assembler support enhancements from HEAD branch: unified ELF,
appro> support for SCO/Caldera targets and for Cygwin shared build.

I think this deserves something in CHANGES...

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken  \ S-168 35  BROMMA  \ T: +46-8-26 52 47
\  SWEDEN   \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/

Unsolicited commercial email is subject to an archival fee of $400.
See  for more info.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [openssl.org #455] [BUG] FreeBSD openssl-0.9.7 I386_ONLY

[Andy Polyakov via RT]

> (cd asm; /usr/local/bin/perl des-586.pl cpp >dx86unix.cpp)
> gcc -E -DOUT asm/dx86unix.cpp | as -o asm/dx86-out.o
> des-586.s: Assembler messages:
> des-586.s:2458: Error: Unimplemented segment type 0 in parse_operand
> des-586.s:2645: Error: Unimplemented segment type 0 in parse_operand
> *** Error code 1

I have reasons to believe that it's not I386_ONLY issue:-) What version
is it? The problem doesn't seem to be present on 4.7
(@login.openssl.org)... What is your assembler version? It must be same
issue as with OpenBSD, see http://www.openssl.org/support/faq.html. That
particular paragraph was updated earlier this night (it's in CVS, but
not on the web yet):

> As of 0.9.7 assembler routines were overhauled for position independence
> of the machine code, which is essential for shared library support. For
> some reason OpenBSD is equipped with an out-of-date GNU assembler which
> finds the new code offensive. To work around the problem, configure with
> no-asm (and sacrifice a great deal of performance) or patch your assembler
> according to http://www.openssl.org/~appro/gas-1.92.3.OpenBSD.patch>.
> For your convenience a pre-compiled replacement binary is provided at
> http://www.openssl.org/~appro/gas-1.92.3.OpenBSD.bin>.

This applied to the *latest* OpenBSD version. Shall we mention "elder
FreeBSD" as well? A.

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

RE: [openssl.org #452] AutoReply: OpenSSL error

[Jimmy Cheng Sze Ngee via RT]

Problem had been resolved. Thanks.

-Original Message-
From: OpenSSL-Bugs [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 12, 2003 8:32 PM
To: [EMAIL PROTECTED]
Subject: [openssl.org #452] AutoReply: OpenSSL error 



   Greetings,
This message has been automatically generated in response to the
creation of a trouble ticket regarding:
"OpenSSL error", 
a summary of which appears below.

There is no need to reply to this message right now.  Your ticket has been
assigned an ID of [openssl.org #452].

Please include the string:

 [openssl.org #452]

in the subject line of all future correspondence about this issue. To do so,

you may reply to this message.

Thank you,


-
Hi,
I had a problem when installing SSL @ SUN Solaris 8
Please advise , thanks.

regards, 
Jimmy

Error message:
***
gcc -I.. -I../.. -I../../include -DOPENSSL_SYSNAME_ULTRASPARC
-DOPENSSL_THREADS -D_RE
ENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -m32 -mcpu=ultrasparc
-O3 -fomit
-frame-pointer -Wall -DB_ENDIAN -DBN_DIV2W -DMD5_ASM  -c  rmd_one.c
ar  r ../../libcrypto.a rmd_dgst.o rmd_one.o
/usr/ccs/bin/ranlib ../../libcrypto.a || echo Never mind.
making all in crypto/des...
gcc -I.. -I../.. -I../../include -DOPENSSL_SYSNAME_ULTRASPARC
-DOPENSSL_THREADS -D_RE
ENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -m32 -mcpu=ultrasparc
-O3 -fomit
-frame-pointer -Wall -DB_ENDIAN -DBN_DIV2W -DMD5_ASM  -c  set_key.c
In file included from des_locl.h:80,
 from set_key.c:66:
/usr/local/lib/gcc-lib/sparc-sun-solaris2.8/2.95.3/include/math.h:5: math.h:
No such
file or directory
*** Error code 1
make: Fatal error: Command failed for target `set_key.o'
Current working directory /opt/tmp/openssl-0.9.7/crypto/des
*** Error code 1
make: Fatal error: Command failed for target `subdirs'
Current working directory /opt/tmp/openssl-0.9.7/crypto
make: *** [sub_all] Error 1


__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [openssl.org #452] AutoReply: OpenSSL error

[Richard Levitte - VMS Whacker]

In message <[EMAIL PROTECTED]> on Mon, 13 Jan 2003 00:43:26 
+0100 (MET), "Jimmy Cheng Sze Ngee via RT" <[EMAIL PROTECTED]> said:

rt> Problem had been resolved. Thanks.

OK.  Thanks.

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken  \ S-168 35  BROMMA  \ T: +46-8-26 52 47
\  SWEDEN   \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/

Unsolicited commercial email is subject to an archival fee of $400.
See  for more info.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [openssl.org #452] AutoReply: OpenSSL error

[Richard Levitte - VMS Whacker via RT]

In message <[EMAIL PROTECTED]> on Mon, 13 Jan 2003 00:43:26 
+0100 (MET), "Jimmy Cheng Sze Ngee via RT" <[EMAIL PROTECTED]> said:

rt> Problem had been resolved. Thanks.

OK.  Thanks.

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken  \ S-168 35  BROMMA  \ T: +46-8-26 52 47
\  SWEDEN   \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/

Unsolicited commercial email is subject to an archival fee of $400.
See  for more info.

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: DJGPP patch for 0.9.7-stable

[Doug Kaufman]

On Sun, 12 Jan 2003, Richard Levitte - VMS Whacker wrote:

> Ah.  Then why did we litter the Makefiles with tests of DJGPP, and why
> whould only the one Doug mentioned be removed?

The tests for DJGPP in the Makefiles are mostly gone. They came in
when the current directory was added to the $PATH for all systems
other than Cygwin. This broke the $PATH for DJGPP because the path
separators are different (";" for DJGPP). The DJGPP changes were
to make DJGPP run in parallel to unix, rather than Cygwin. Now the
current directory is added only for Cygwin, so no special test for
DJGPP is necessary. It sounds like the original code that added the
current directory for everything except Cygwin wasn't correct, so
the problem for DJGPP has now disappeared. It looks like the tests
for DJGPP in apps and test should also be removed. They originally
specified the opposite of what was done for Cygwin; now they are doing
the same as Cygwin.
Doug
-- 
Doug Kaufman
Internet: [EMAIL PROTECTED]

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [openssl.org #455] [BUG] FreeBSD openssl-0.9.7 I386_ONLY

[(Dirk Meyer) via RT]

> > (cd asm; /usr/local/bin/perl des-586.pl cpp >dx86unix.cpp)
> > gcc -E -DOUT asm/dx86unix.cpp | as -o asm/dx86-out.o
> > des-586.s: Assembler messages:
> > des-586.s:2458: Error: Unimplemented segment type 0 in parse_operand
> > des-586.s:2645: Error: Unimplemented segment type 0 in parse_operand
> > *** Error code 1
> 
> I have reasons to believe that it's not I386_ONLY issue:-) What version
> is it? The problem doesn't seem to be present on 4.7
> (@login.openssl.org)... What is your assembler version? It must be same
> issue as with OpenBSD, see http://www.openssl.org/support/faq.html. That
> particular paragraph was updated earlier this night (it's in CVS, but
> not on the web yet):

GNU assembler version 1.92.3, FreeBSD $Revision: 1.4 $

> > As of 0.9.7 assembler routines were overhauled for position independence
> > of the machine code, which is essential for shared library support. For
> > some reason OpenBSD is equipped with an out-of-date GNU assembler which
> > finds the new code offensive. To work around the problem, configure with
> > no-asm (and sacrifice a great deal of performance) or patch your assembler
> > according to http://www.openssl.org/~appro/gas-1.92.3.OpenBSD.patch>.
> > For your convenience a pre-compiled replacement binary is provided at
> > http://www.openssl.org/~appro/gas-1.92.3.OpenBSD.bin>.
> 
> This applied to the *latest* OpenBSD version. Shall we mention "elder
> FreeBSD" as well? A.

it fails at least on FreeBSD 2.2.x

kind regards Dirk

- Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany
- [[EMAIL PROTECTED]],[[EMAIL PROTECTED]],[[EMAIL PROTECTED]]

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

[Doug Kaufman]

On Sun, 12 Jan 2003, Andy Polyakov wrote:

> > > > I tried this patch on DJGPP both as normally compiled and also using
> > > > the asm modules (put ${x86_out_asm} in the DJGPP config-string
> > >   ^^^ Oh! I missed that. I mean the fact that they are not
> > > actually engaged in the default configuration. Any particular reason
> > > why?
> > 
> > The only reason is to maintain 386 compatibility. The last time I
> > asked (I think it was about a year ago), there was a question as to
> > whether 386 incompatible instructions were used in the asm files, even
> > if "386" was specified in the Configure options.
> 
> If you './Configure ... DJGPP 386', then pure 386 asm code will be
> generated. Well, it's all about single instruction, bswapl to be
> specific... A.

In that case, it probably makes sense to make the asm code the
default in DJGPP also. This should just take a change in the DJGPP
config-string in Configure to put ${x86_out_asm} into the (currently
blank) next field after ${x86_gcc_opts}.
Doug
-- 
Doug Kaufman
Internet: [EMAIL PROTECTED]

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]