First of all it would facilitate if you could file a single problem per report. In which the person who is considering to close the ticket won't end up judging over things he doesn't feel like capable of judging. Like me over your previous RT#410:-) I mean e.g. BN_sqr failure was exactly my cup of tea, but not the rest [I don't even have an access to HP-UX/PA-RISC machine]. But as I was the last one to "touch" the ticket I felt it would be mine responsibility to decide if it should be closed.
> i'm having a few problems building OpenSSL 0.9.7 on a HP-UX 11.00 machine > using the HP Ansi C compiler. here's a list of the issues i've noticed so > far (i've listed configuration options and error messages below): > > 1) when compiling for hpux-parisc2-cc target with no-asm option > BN_kronecker test fails. As implied in RT#410 closing note it smells like a compiler bug. From my personal experience HP compilers seldom work out-of-the-box and usually require patching. In either case do try to lower the optimization level [as INSTALL suggests]! > 2) error messages during 'make depend' when not using gcc and makedepend I have *no* comment on this one. > 3) shared library linking fails with hpux-parisc2-cc target. 'cd ./crypto/bn; rm asm/pa-risc2.o; make -n'. What is the command line issued to compile asm/pa-risc2.o? Does it have +Z? Copy-n-paste command line adding +Z and execute it. Does it execute? If it does, 'cd ../../; make'. Does it complete? A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
