> >If you can really confirm that './config -t' fails to print
> "configuring
> >for hpux64-parisc-gcc" on your system,
>
> nmcmadam:/opt/patches/openssl-0.9.7c> ./config -t
> Operating system: 9000/800-hp-hpux10
^^ Well, HP-UX 11.x user might find
this inappropriate, but it doesn't really gives the reason to tell apart
10.0 and every possible 11.x. Changing this particular line to
9000/800-hp-hpux1x instead is probably more appropriate...
> Configuring for hpux-parisc-gcc
> /usr/contrib/bin/perl ./Configure hpux-parisc-gcc -D_REENTRANT
>
> >then submit output from 'gcc -v -E -x c /dev/null' command.
>
> nmcmadam:/opt/patches/openssl-0.9.7c> gcc -V -E -x c /dev/null
The line was with -v, not -V.
> gcc: couldn't run `hppa64-hp-hpux11.11-gcc--E': No such file or directory
> ^^^
> (*hm seems like my gcc copy may have a problem! would this cause the
> 'config -t' mistake?*)
No "would" in the last sentense. The question is "does this cause the
problem?" and the answer is "yes, it does."
Why does it want to run *-gcc--E? Can you preprocess any .c file with
just 'gcc -E somefile.c'? A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
