Kaspar, I'm aware of the previous thread. Thank you for citing it here for convenience.
I'm working backwards from the fact that there are multiple define's related to the target platform, not just USE_64/NSS_USE_64 but also NSS_X64 and NSS_X86, which do indeed have a few other appearances in freebl source files. You're absolutely right that these aren't that frequent, but I'm not convinced that changing these cases from pre-processor to runtime management is a preferable solution overall. I also doubt that the question is really one of how many cases but of what techniques are preferable to manage those cases, and it's not at all clear why the choice of technique to solve an OS X-specific problem should require changes in techniques with general application that I'd expect to support maintability and portability. I don't see what's so preferable about marginally optimising the mechanics of this on OS X if it looks to make far more fundamental changes in the code and the build process that do not fundamentally jibe with their apparent design philosophy. Why would it be so preferable to use gcc than lipo in the first place, given that the former appears to be a more disruptive approach? Regards, Bayard On 26 Mar 2011, at 07:58, Kaspar Brand wrote: > On 23.03.2011 19:55, Bayard Bell wrote: >> I've been doing some hacking to sort out remaining issues with >> getting 32-bit build support on OS X 10.6, allowing for universal >> builds > > [...] > >> There was a thread on this subject earlier this year, and my >> conclusion from that was that there was general support amongst the >> developers for sorting this out. > > Correct. That's why I would suggest to follow up on this thread, and not > create a new one. > > Rather than bringing lipo into play, I would prefer a solution which > would simply rely on setting CC="gcc -arch x86_64 -arch i386", as > proposed in > news://news.mozilla.org:119/[email protected]. > > The only obstacle for this are a few uses of NSS_USE_64 in freebl, I > think (see http://mxr.mozilla.org/mozilla/search?string=NSS_USE_64) - in > particular the one in drbg.c. > > Kaspar > -- > dev-tech-crypto mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-tech-crypto
PGP.sig
Description: This is a digitally signed message part
-- dev-tech-crypto mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-crypto
