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)" \
203 CC="$(CC)" \
204 CCC="$(CXX)" \
205 LINK="$(LD)" \
206 AS="$(AS)" \
207 AR='$(AR) $(AR_FLAGS:[EMAIL PROTECTED]@)' \
208 RANLIB="$(RANLIB)" \
209 RC="$(RC) $(RCFLAGS)" \
210 OS_ARCH="$(OS_ARCH)" \
211 CPU_ARCH="$(TARGET_CPU)" \
212 $(NULL)
213 SKIP_CHK=1
214 endif
Yes, and this is the cause of the third issue in my original post :-( I
wonder why NSS uses LINK instead of LD?
NSS uses LD on Unix (including Linux and Mac OS X), and
LINK on Windows, to refer to the linker. The use of RC
(resource compiler, a tool used only on Windows) in the
above makefile snippet also suggests that the
cross-compilation targets included Windows. See
http://lxr.mozilla.org/security/source/security/coreconf/WIN32.mk#45http://lxr.mozilla.org/security/source/security/coreconf/WIN32.mk#45
Wan-Teh
_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
