Closed
Bug 1020117
Opened 10 years ago
Closed 9 years ago
VC14 configure error: Unable to parse cl -showIncludes prefix. This compiler's locale has an unsupported formatting.
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1026858
People
(Reporter: xavier114fch, Unassigned)
Details
Attachments
(2 files)
I am using Visual Studio 2014 CTP (VC14) and cannot get Firefox to pass through configure. 0:36.79 configure: error: Unable to parse cl -showIncludes prefix. This compiler's locale has an unsupported formatting. 0:36.79 ------ config.log ------ 0:36.82 configure:25740: cl -o conftest -LARGEADDRESSAWARE -NXCOMPAT -DYNAMICBASE -SAFESEH @conftest.list kernel32.lib user32.lib gdi32.lib winmm.lib wsock32.lib advapi32.lib secur32.lib netapi32.lib 1>&5 0:36.82 Microsoft (R) C/C++ Optimizing Compiler Version 19.00.21730.1 for x86 0:36.82 Copyright (C) Microsoft Corporation. All rights reserved. 0:36.82 0:36.82 cl : Command line warning D9035 : option 'o' has been deprecated and will be removed in a future release 0:36.82 cl conftest.obj 0:36.82 0:36.82 cl : Command line warning D9002 : ignoring unknown option '-LARGEADDRESSAWARE' 0:36.82 cl : Command line warning D9002 : ignoring unknown option '-NXCOMPAT' 0:36.82 cl : Command line warning D9002 : ignoring unknown option '-SAFESEH' 0:36.82 Microsoft (R) Incremental Linker Version 14.00.21730.1 0:36.82 Copyright (C) Microsoft Corporation. All rights reserved. 0:36.82 0:36.82 /out:conftest.exe 0:36.82 /out:conftest.exe 0:36.82 conftest.obj 0:36.82 kernel32.lib 0:36.82 user32.lib 0:36.82 gdi32.lib 0:36.82 winmm.lib 0:36.82 wsock32.lib 0:36.82 advapi32.lib 0:36.82 secur32.lib 0:36.82 netapi32.lib 0:36.82 configure: error: Unable to parse cl -showIncludes prefix. This compiler's locale has an unsupported formatting. 0:36.83 *** Fix above errors and then restart with\ 0:36.83 "e:/mozilla-build/mozmake/mozmake.EXE -f client.mk build" 0:36.85 client.mk:362: recipe for target 'configure' failed 0:36.85 mozmake.EXE: *** [configure] Error 1 There was no such error using Visual Studio 2013 Update 3 CTP1 (VC12).
Reporter | ||
Comment 1•10 years ago
|
||
Build log from "mach configure"
Reporter | ||
Comment 2•10 years ago
|
||
Config.log of the same run
Comment 3•10 years ago
|
||
Create a foo.c file with the following content: #include <stdio.h> Then run the following command: cl -c -nologo -Fonul -showIncludes foo.c What is the output?
Reporter | ||
Comment 4•10 years ago
|
||
I am using dummy-hello.c and this is the result. $ cl -c -nologo -Fonul -showIncludes dummy-hello.c dummy-hello.c Note: including file: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INC LUDE\stdio.h Note: including file: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\IN CLUDE\corecrt.h Note: including file: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\I NCLUDE\vcruntime.h Note: including file: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ INCLUDE\sal.h Note: including file: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC \INCLUDE\ConcurrencySal.h Note: including file: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ INCLUDE\vadefs.h Note: including file: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\IN CLUDE\corecrt_wstdio.h Note: including file: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\I NCLUDE\corecrt_stdio_config.h I think the regex matches with these 2 lines: Note: including file: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INC LUDE\stdio.h Note: including file: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\IN CLUDE\corecrt_wstdio.h so $_CL_STDIO_PATH becomes C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\stdio.h C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\corecrt_wstdio.h and the test statement always returns true.
Comment 5•10 years ago
|
||
see bug1026858
Updated•9 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•