> > > > ... wondered what
> > > > happens if you attempt to compile it with -DSHA_XARRAY (as that's
> > > > actually what is *essentially* different between 0.9.4 and 0.9.5).
> > >
> > > Ok, the compilation at +O3 has now jumped over the sha_dgst.c hurdle
> >
> > OK, the picture is clear. It makes sense to define common macro, say
> > MD32_XARRAY, on platform basis. Can you help with predefined macros on
> > HP-UX C?
>
> man cpp yields:
> ... All HP-UX
> systems have the symbols PWB, hpux, unix, _PWB, __hpux,
> and __unix defined. Each system defines at least one
> hardware variant, as appropriate...
>
> So hpux and or __hpux might be appropriate.
But they'll be defined on gcc as well... It looks like there're no
predefined identifying HP C compiler, huh? Well, whatever...
> As for my personal preferences: I would prefer to define this -DMD32_XARRAY
> in "Configure" so that the mechanism is visible and documented.
Makes sense... Grab snapshot later today and check it out. BTW, what are
you used to, config or Configure? Note that there're new unified config
lines, namely hpux-parisc-cc, hpux-parisc-gcc and hpux64-parisc-cc.
Cheers. Andy.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
