On 2015-06-25 5:24 PM, Alex wrote:
Attempting to compile Firefox with clang-cl works great up until freebl, where
it chokes. This is attempting to build a 64-Bit version with 64-Bit clang. Both
versions 3.6.0-r225071 and 3.7.0-r240278 were used, but with the same errors
from both.
I used the following mozconfig: http://pastebin.com/04XpKvYN
Which produces the following error: http://pastebin.com/86gdM1Wj
It looks like the fail point is 40:37.42 rijndael.obj : error LNK2019:
unresolved external symbol _xgetbv referenced in function AES_InitContext
which seems to be caused by clang not using it's own headers, rather it used
Visual C++'s.
Directing clang to its own headers with
-I/c/PROGRA~1/LLVM/lib/clang/3.7.0/include seems to fix that issue but create
another error at the same point as can be seen here:
http://pastebin.com/CqiafhUG
I feel like this is either an environment error on my part or clang-cl isn't
doing something correctly? Has anyone else ran into this issue?
It looks like when I fixed bug 1041326, I forgot about 64-bit builds.
:( Check out this code please:
<https://hg.mozilla.org/mozilla-central/rev/e1c5c185b707#l6.12>. This
sets the INTEL_GCM_CLANG_CL flag if we detect clang-cl in the 32-bit
mode, so you probably want to add a similar code to the else branch of
the condition that checks USE_64 in the same file.
If that fixes the error for you, I would appreciate if you would file a
bug and submit this fix to NSS.
Thanks!
_______________________________________________
dev-builds mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-builds
