> We have this working on HPUX ia64 in both 32 and 64 bit modes. > You'll have to manually "Configure" anyway, there are three supported > modes, 32 bit , 64 bit, and pa_risc, all of which are supported by the base > OS.
./config tells apart IA-64 and PA-RISCs as well, and then it consciously defaults to 64-bit IA-64 build if executed on IA-64 machine and to 32-bit PA-RISC build - on PA-RISC. > Autodetection is going to give the wrong answer 2 times in 3. ./config is expected to auto-detect most appropriate option for the platform it's being executed on. Can you confirm that it actually fails to detect platform as depicted above? I.e. hpux64-ia64-cc on IA-64 machine and hpux-parisc2-cc at PA-RISC2 machine? Blended builds (which would execute on both PA-RISC1.1 and 2.0 in this example), builds for another ABI (32-bit vs. 64-bit) or cross-platform builds (PA-RISC code on IA-64) were never ./config's domain, but something for user to think about. In other words you can't expect ./config to prepare for 3 builds (or why not 5: 64-bit IA-64, 32-bit IA-64, 64-bit PA-RISC2.0, 32-bit PA-RISC2.0, 32-bit blended PA-RISC?) and should invoke './Configure <proper-line>; make; ...' multiple times if so required. At least for the time being. We have to decide what we want to discuss in this particular context. ./config's intended behaviour or bugs in it. > The IBM patch with the code in it is available, but it's too big to post to > this list. Post it to openssl-team then:-) A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
