On 01/19/2011 10:36 PM, Kaspar Brand wrote: > On 20.01.2011 05:08, Nathan Craike wrote: > >> I'd eventually like to include the built libraries in software >> deployed an any machine running Mac OS X 10.6, which may be Intel >> 32-bit or 64-bit machines, so a build which works on both >> architectures would be preferred (either 32-bit or some kind of >> universal binary, I assume). > That's certainly doable, but I don't think the NSS build system has > support for building universal binaries (you'd have to fiddle with lipo > yourself). I think it depends on what the Mac compiler kicks out. On Windows or Linux, the non-64 bit builds automatically set the compiler to produce 32-bit binaries unless the USE_64 is set.
My guess is that no one has set the compiler flags correct for building 32-bit binaries on Mac 64. >> Should I be able to build the 32-bit version of NSS? Should this >> assertion be failing? > I also ran into this previously, and added "-DNS_PTR_GT_32" to the > "OS_REL_CFLAGS = -Di386" line in Darwin.mk. Not sure if that's the > proper way of fixing things, though. My guess is, no. Intel platforms do not have greater then 32 bit pointers when running in 32 bit mode, so I suspect you are building 64 bit binaries. NS_PTR_GT_32 or NS_PTR_LE_32 are variables which you set if your native build is a 32 build but your native pointer is actually later or your native build is 64 bit, but the pointer is less. I think you just wound up producing 64 bit binaries with the 32 bit directory names. If you have the proper changes to coreconf to produce 32 bits on a Mac 64 bit system, we would certainly be interested. bob > Kaspar
-- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
