> > >'./Configure hpux64-parisc-gcc -m64' work? > > > > <snip> > > nmcmadam:/opt/patches/openssl-0.9.7c> ./Configure hpux64-parisc-gcc -m64 > > ... > > Configured for hpux64-parisc-gcc. > > nmcmadam:/opt/patches/openssl-0.9.7c> > > </snip> > > > > Does that help? > > >Not really:-) What happens if you actually run 'make'? > > It fails make (see output below) > > >Does 'gcc -m64'actually work? > > No. (see output below).
Does it mean that your gcc without any options generate ELF64 object modules then? Because if it does, then original ./config should have worked and configured for 64-bit build [without even checking for kernel bit-ness!]. If gcc without extra option doesn't generate ELF64 object modules, then it's no point to check for kernel bit-ness, *unless* we know what command line option makes gcc generate different object modules. So if you *know* that your gcc is capable of generating both ELF64 and 32-bit object modules, then you should figure out what is the command line option and tell us. If there is no such option, then ./config does its best as it is now. > >Are resulting object modules ELF64? > > How can I check it? Well, it was least exepcted to get such question from somebody who has suggested to run 'file /stand/vmunix':-) With 'file some.o' of course! > nmcmadam:/opt/patches/openssl-0.9.7c> ./Configure hpux64-parisc-gcc > ... > Configured for hpux64-parisc-gcc. > > "make" finish successfully. What does `file apps/openssl' print then? A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
