Wan-Teh Chang wrote:
>> I can point you to the relevant Mozilla makefile:
>> http://lxr.mozilla.org/security/source/security/manager/Makefile.in#199
>>
>> You'll see that the Mozilla developers override these make variables
>> used by the NSS coreconf build system when cross-compiling NSS:
>>
>>
> - It can be quite difficult for someone who is not familiar with the
> code to interpret. The feature exists to help the code's developers
> debug the code, not as a general SSL line monitoring tool (which
> ssltap is).
>
ok...I see. I apologize to Pedro then, I am more of a developer than
a
Neil wrote:
Wan-Teh Chang wrote:
You'll see that the Mozilla developers override these make variables
used by the NSS coreconf build system when cross-compiling NSS:
199 ifdef CROSS_COMPILE
200 DEFAULT_GMAKE_FLAGS += \
201 NSINSTALL="$(NSINSTALL)" \
202 NATIVE_CC="$(HOST_CC)"
Wan-Teh Chang wrote:
You'll see that the Mozilla developers override these make variables
used by the NSS coreconf build system when cross-compiling NSS:
199 ifdef CROSS_COMPILE
200 DEFAULT_GMAKE_FLAGS += \
201 NSINSTALL="$(NSINSTALL)" \
202 NATIVE_CC="$(HOST_CC)" \
203
Wan-Teh Chang wrote:
NSS uses LD on Unix (including Linux and Mac OS X), and LINK on
Windows, to refer to the linker.
It also uses $LINK_DLL on Windows and $MKSHLIB everywhere else. How
inconsistent :-(
--
Warning: May contain traces of nuts.
___
5 matches
Mail list logo