At 10:50 AM +0100 11/29/00, Richard Levitte - VMS Whacker wrote:
>From: Mark Morrill <[EMAIL PROTECTED]>
>
>I'm sorry, but I did respond to that kind of question some time ago.
>The problem is, I think no-one in the development team has access to
>any MacOS X machine, so checking things out is a bit of a problem.
>
>The error at hand is very easily fixed if there's a way to identify
>MacOS X through some C macro.  OpenBSD, for example, is identifiable
>through the macro __OpenBSD__.  Is there such a thing for MacOS X?
>
>Please help us find that kind of information, and in turn, we can help
>you fix the problem!
>

I worked through this problem just this week.   There's one line in 
apps/speed.c that needs to have the __APPLE__ macro added to it. 
This isn't the sanctioned macro to use for identifying MacOSX or 
MacOSXServer operating systems, but it is expedient.

In line 90 of speed.c, you need to add "&& !defined(__APPLE__)" to 
the list of conditionals that determine whether to define the TIMEB 
symbol.

#if defined(__FreeBSD__)
# define USE_TOD
#elif !defined(MSDOS) && (!defined(VMS) || defined(__DECC))
# define TIMES
#endif
#if !defined(_UNICOS) && !defined(__OpenBSD__) && !defined(sgi) && 
!defined(__Fr
eeBSD__) && !(defined(__bsdi) || defined(__bsdi__)) && !defined(_AIX) 
&& !define
d(MPE) && !defined(__APPLE__)
# define TIMEB
#endif

The recommended way to deal with this on Mac OS is to define your 
symbol identifying the OS.  Inventing a symbol like "__MACOSX__", 
make the edit to apps/speed.c described above, substituting 
"__MACOSX__" for "__APPLE__".  Then run config again, with these 
parameters:  ./config no-threads -D__MACOSX__

Hope this helps.  I have OpenSSL 0.9.6 running on my MOSX box, so it 
should work for you too.

Bill

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to