Re: Compilation error on OpenStep 4.0
On Sat, Mar 18, 2000 at 06:42:21PM -0700, Francisco A Tomei Torres wrote: grep clock time.h typedef unsigned long int clock_t; clock_t clock(void); clock_t clock(); And can you locate CLOCKS_PER_SEC anywhere in some header file? Also, what does the clock() manual page say about what the return value means? __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Compilation error on OpenStep 4.0
Hi, Francisco A. Tomei Torres [EMAIL PROTECTED]: cc -I../include -O -Wall -c ssltest.c -o ssltest.o ssltest.c: In function `main': ssltest.c:504: `CLOCKS_PER_SEC' undeclared (first use this function) Weird, this should be defined in time.h on every standard C system (it's not a POSIX special or something). Please grep through the standard header files to see if you can find this symbol anywhere. Also please read the manual page for the C function clock() and look for hints; it should say something like this: RETURN VALUE The value returned is the CPU time used so far as a clock_t; to get the number of seconds used, divide by CLOCKS_PER_SEC. In any case, please tell us if you've found something or not. NEXTSTEP/OPENSTEP has no define for CLOCKS_PER_SEC. There is a CLK_TCK define in "times.h": #ifdef _NEXT_SOURCE #import stddef.h #define CLK_TCK 64 #endif /* _NEXT_SOURCE */ and this is from the apache source code: #ifdef NEXT #if (NX_CURRENT_COMPILER_RELEASE == 410) #ifdef m68k #define HZ 64 #else #define HZ 100 #endif #else #include machine/param.h #endif #endif /* NEXT */ Maybe this helps? Bye, Juergen __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Compilation error on OpenStep 4.0
Hi, > On Sat, Mar 18, 2000 at 06:42:21PM -0700, Francisco A Tomei Torres wrote: > > > grep clock time.h > > typedef unsigned long int clock_t; > > clock_t clock(void); > > clock_t clock(); > > And can you locate CLOCKS_PER_SEC anywhere in some header file? > Also, what does the clock() manual page say about what the return > value means? The is no manual page for the function clock() and there is no CLOCKS_PER_SEC define (NEXTSTEP/OPENSTEP). Bye, Juergen __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Compilation error on OpenStep 4.0
cc -I../include -O -Wall -c ssltest.c -o ssltest.o ssltest.c: In function `main': ssltest.c:504: `CLOCKS_PER_SEC' undeclared (first use this function) ssltest.c:504: (Each undeclared identifier is reported only once ssltest.c:504: for each function it appears in.) make[1]: *** [ssltest.o] Error 1 make[1]: Target `all' not remade because of errors. make[1]: Leaving directory `/root/temp/openssl-0.9.5a-beta2/test' make: *** [all] Error 1 __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Compilation error on OpenStep 4.0
Francisco A. Tomei Torres [EMAIL PROTECTED]: cc -I../include -O -Wall -c ssltest.c -o ssltest.o ssltest.c: In function `main': ssltest.c:504: `CLOCKS_PER_SEC' undeclared (first use this function) Weird, this should be defined in time.h on every standard C system (it's not a POSIX special or something). Please grep through the standard header files to see if you can find this symbol anywhere. Also please read the manual page for the C function clock() and look for hints; it should say something like this: RETURN VALUE The value returned is the CPU time used so far as a clock_t; to get the number of seconds used, divide by CLOCKS_PER_SEC. In any case, please tell us if you've found something or not. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Compilation error on OpenStep 4.0
grep clock time.h typedef unsigned long int clock_t; clock_t clock(void); clock_t clock(); At 01:43 AM 3/25/00 +0100, Bodo Moeller wrote: Francisco A. Tomei Torres [EMAIL PROTECTED]: cc -I../include -O -Wall -c ssltest.c -o ssltest.o ssltest.c: In function `main': ssltest.c:504: `CLOCKS_PER_SEC' undeclared (first use this function) Weird, this should be defined in time.h on every standard C system (it's not a POSIX special or something). Please grep through the standard header files to see if you can find this symbol anywhere. Also please read the manual page for the C function clock() and look for hints; it should say something like this: RETURN VALUE The value returned is the CPU time used so far as a clock_t; to get the number of seconds used, divide by CLOCKS_PER_SEC. In any case, please tell us if you've found something or not. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Compilation error on OpenStep 4.0
Hi, > > FWIW ssize_t is a POSIX type, so... the bug isn't in OpenSSL.. ;-) > > I don't know if NeXT claims to be POSIX compliant, but Windows > certainly never was. No, NeXT doesn't claim to be POSIX compliant, in fact the POSIX-Support from NeXT/Apple is completely broken in NEXTSTEP and OPENSTEP. Bye, Jürgen Möllenhoff __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Compilation error on OpenStep 4.0
On Tue, Mar 07, 2000 at 02:14:05PM -0700, Francisco A Tomei Torres wrote: bss_bio.c:209: undefined type, found `ssize_t' I've encountered the same problem on another platform. Expect a fix shortly. (For now, you can just replace all occurences of "ssize_t" with "long"). __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Compilation error on OpenStep 4.0
Ulf Möller wrote: On Tue, Mar 07, 2000 at 02:14:05PM -0700, Francisco A Tomei Torres wrote: bss_bio.c:209: undefined type, found `ssize_t' I've encountered the same problem on another platform. Expect a fix shortly. (For now, you can just replace all occurences of "ssize_t" with "long"). FWIW ssize_t is a POSIX type, so... the bug isn't in OpenSSL.. ;-) All of this could be avoided if we just would use autoconf!!! -- QUI ME AMET, CANEM MEUM ETIAM AMET __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: Compilation error on OpenStep 4.0
On Fri, Mar 10, 2000 at 12:58:43PM -0800, Michael Sierchio wrote: FWIW ssize_t is a POSIX type, so... the bug isn't in OpenSSL.. ;-) I don't know if NeXT claims to be POSIX compliant, but Windows certainly never was. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Compilation error on OpenStep 4.0
snapshot of 3-9 cc -I.. -I../../include -O -Wall -c b_print.c -o b_print.o b_print.c:205: warning: redefinition of macro MAX /NextLibrary/Frameworks/System.framework/Headers/bsd/libc.p:0: warning: this is the location of the previous definition cc -I.. -I../../include -O -Wall -c bss_bio.c -o bss_bio.o bss_bio.c:209: undefined type, found `ssize_t' bss_bio.c:247: undefined type, found `ssize_t' make[2]: *** [bss_bio.o] Error 1 make[2]: Leaving directory `/root/temp/openssl-SNAP-2309/crypto/bio' make[1]: *** [subdirs] Error 1 make[1]: Leaving directory `/root/temp/openssl-SNAP-2309/crypto' make: *** [all] Error 1 __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
