Why the need for FREEBL_RECURSIVE_BUILD? I did set USE_PURE_32 to 1 and did get preety far with building a pure 32 freebl lib but once built, it looks like it gets built again... First a lib is built under HP-UXB.11.00_gcc_OPT.OBJ/HP-UXpure32/HP-UXB.11.00_gcc_OPT.OBJ but then another build attempt is made for HP-UXB.11.00_gcc_OPT.OBJ/HP-UXpure32/HP-UXB.11.00_gcc_OPT.OBJ/HP-UXpure32...
"Nelson B. Bolyard" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED].; > Patrick wrote: > > > > What about the message saying " to report this error as a bug"? > > That message comes from the program that gcc invoked the process the .s > file. That program is probably "gas", the gnu assembler. It is telling > you to report an error to the people responsible for the gas assembler > itself. > > > Has anyone seen these porting issues with the > > /nsprpub/pr/src/md/unix/os_HPUX.s file on HP11? > > AFAIK, no one has ever before tried to port NSS to HPUX without using HP's > compilers and assemblers. > > There are numerous Unix platforms on which it is necessary to use hand > optimized assembler code to get anything near reasonable performance for > RSA, DSA, DH and other algorithms that use very big numbers (e.g. 1024 bit > integers and larger). Each of those platforms has its own native assembler > language that is supported by the vendor's own assembler program. The gnu > assembler is also available for many (perhaps all) of those platforms, but > generally gnu's assembler language has a different syntax than the vendor's > own assembler language, so that a single assembler source file typically > cannot be used both with the vendor's assembler and with gnu's assembler. > Consequently separate .s files are required for each assembler. > > NSS has assembler files for several platforms/CPUs, including HP PA_Risc > 2.0, UltraSparc v8 and UltraSparc v9, various MIPS cpus, and Intel x86. > Of these, the only platform/CPU on which separate NSS assembler source > files hav been developed for vendor and gnu assemblers (AFAIK) is x86. > > IINM, HP's compiler/assembler tools that we use are installed in > /opt/ansic/bin, which we prepend to our path. Have you looked there? > > You can build for HPUX without using any assembler code. However, I'd > expect it to be pretty slow. > > I no longer have an HPUX system on which to do test builds. So the idea > I have, below, for building without any assembler code may or may not > work. > > I _think_ that if you replace the entire content of the file config.mk > with a single line that reads simply > > USE_PURE_32 = 1 > > that might work. > > > -- > Nelson Bolyard Netscape > Disclaimer: I speak for myself, not for Netscape
