[openssl.org #433] 0.9.7 compilation problem with Borland C++ 5.5

I've analysed this further and the cause seems to be that it bcc 5.5 complains about taking the address of a structure that doesn't have a complete definition. For example the following wont compile: typedef struct FOO_st FOO; extern FOO bar; FOO *pbar; pbar = bar; but it has no problems on

Re: [openssl.org #433] 0.9.7 compilation problem with Borland C++ 5.5

In message [EMAIL PROTECTED] on Tue, 14 Jan 2003 14:49:31 +0100 (MET), Stephen Henson via RT [EMAIL PROTECTED] said: rt I've analysed this further and the cause seems to be that it bcc 5.5 rt complains about taking the address of a structure that doesn't have a rt complete definition. rt rt

Re: [openssl.org #433] 0.9.7 compilation problem with Borland C++5.5

Richard Levitte - VMS Whacker via RT wrote: In message [EMAIL PROTECTED] on Tue, 14 Jan 2003 14:49:31 +0100 (MET), Stephen Henson via RT [EMAIL PROTECTED] said: rt I've analysed this further and the cause seems to be that it bcc 5.5 rt complains about taking the address of a structure that

Re: [openssl.org #433] 0.9.7 compilation problem with Borland C++5.5

Yes that's what I thought. Any ANSI C experts care to comment on whether that is legal or not? It's as legal as this: extern int foo(int); int (*fp)(int) = foo; :) __ OpenSSL Project

Re: [openssl.org #433] 0.9.7 compilation problem with Borland C++ 5.5

Yes that's what I thought. Any ANSI C experts care to comment on whether that is legal or not? It's as legal as this: extern int foo(int); int (*fp)(int) = foo; :) __ OpenSSL Project

[openssl.org #433] 0.9.7 compilation problem with Borland C++ 5.5

OK, since the consensus seems to be a compiler bug and a workaround has been checked in I'll resolve this ticket. __ OpenSSL Project http://www.openssl.org Development Mailing List

Re: [openssl.org #433] 0.9.7 compilation problem with Borland C++5.5

[[EMAIL PROTECTED] - Fri Jan 3 06:45:12 2003]: I'm trying to compile 0.9.7 with Borland C++ 5.5 and NASM 0.98.35 on Windows XP Professional SP1 with all updates. .\crypto\x509\x_all.c: Error E2450 .\crypto\x509\x_all.c 72: Undefined structure 'ASN1_ITEM_st' This

Re: [openssl.org #433] 0.9.7 compilation problem with Borland C++ 5.5

[[EMAIL PROTECTED] - Fri Jan 3 06:45:12 2003]: I'm trying to compile 0.9.7 with Borland C++ 5.5 and NASM 0.98.35 on Windows XP Professional SP1 with all updates. .\crypto\x509\x_all.c: Error E2450 .\crypto\x509\x_all.c 72: Undefined structure 'ASN1_ITEM_st' This

[openssl.org #433] 0.9.7 compilation problem with Borland C++ 5.5

[[EMAIL PROTECTED] - Fri Jan 10 21:48:32 2003]: I tried 0.9.7 before succesfully compiling 0.9.6h. As Doug Kaufman suggested for some reason asn1t.h doesn't get included. I had to manually edit a dozen source files. I also have Cygwin in c:\cygwin, but my PATH shows:

[openssl.org #433] 0.9.7 compilation problem with Borland C++ 5.5

[[EMAIL PROTECTED] - Fri Jan 3 06:45:12 2003]: I'm trying to compile 0.9.7 with Borland C++ 5.5 and NASM 0.98.35 on Windows XP Professional SP1 with all updates. I did perl Configure BC-32 no-idea no-mdc2 no-rc5 ms\do_nasm make -f ms\bcb.mak It fails at:

Re: [openssl.org #433] 0.9.7 compilation problem with Borland C++ 5.5

On Fri, 10 Jan 2003 21:27:56 +0100 (MET), Lutz Jaenicke via RT [EMAIL PROTECTED] said: [[EMAIL PROTECTED] - Fri Jan 3 06:45:12 2003]: I'm trying to compile 0.9.7 with Borland C++ 5.5 and NASM 0.98.35 on Windows XP Professional SP1 with all updates. I did perl Configure

Re: [openssl.org #433] 0.9.7 compilation problem with Borland C++ 5.5

Just to inform you that 0.9.6h compiled with the same setup. I don't know if the following are serious: bcc32 -otmp32\c_zlib.obj -Iinc32 -Itmp32 -DWIN32_LEAN_AND_MEAN -q -w-aus -w-par -w-inl -c -tWC -tWM -DWINDOWS -DWIN32 -DL_ENDIAN -DDSO_WIN32 -O2 -ff -fp -DBN_ASM