Closed
Bug 523861
Opened 16 years ago
Closed 9 years ago
Failing to build code coverage build on Windows 32
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: murali, Unassigned)
Details
I am using a standard VMImage of WinXP for building on windows. Debug build builds well. Code coverage build using Microsoft Visual Studio Team Server edition happens well. But John O'Duinn and I discussed about this approach and found out that this would pose a lot of re-factoring risks to RE setup [ if we upgrade to MSVC9 Team Server Edition ].
So, I started looking at the next most popular alternative. Trying to build using 'BullseyeCoverage' tool.
BullseyeCoverage provides wrappers for 'cl', CC, C++ etc., that help to create a build that is instrumented. So, BullseyeCoverage sits ahead of the real MSVC9 'cl' in the %PATH%.
However, out build sanity checker that runs when we issue the command
'make -f client.mk build' fails with the following error
configure: error: This version of the MSVC compiler, 7.13.4
15.00.30729.01
9.00.30729.01 , is unsupported.
*** Fix above errors and then restart with "make -f client.mk build"
make[1]: *** [configure] Error 1
make[1]: Leaving directory `/c/projects/mozilla-central/src'
make: *** [/c/projects/mozilla-central/src/../dbg/Makefile] Error 2
What is the work around?
Thanks
Murali
Comment 1•16 years ago
|
||
I think bug is probably INVALID or WONTFIX, but if it isn't, it's Build Config, not releng
Component: Release Engineering → Build Config
Product: mozilla.org → Core
QA Contact: release → build-config
Version: other → unspecified
| Reporter | ||
Comment 2•16 years ago
|
||
Can I make changes to Build config ?
Comment 3•16 years ago
|
||
you can definitely submit a patch
Comment 4•16 years ago
|
||
Murali, it sounds easier to me to have a dedicated slave with MSVC 9 Team edition just for building code coverage builds... is that not possible?
That said, changing the configure test to account for a cl wrapper is not impossible, you just need to change the logic in configure.in to account for different/unexpected output from the wrapper than from MSVC itself.
Comment 5•9 years ago
|
||
Old bug against ancient, now unsupported toolchain. Resolving.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Updated•8 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•