Closed
Bug 946189
Opened 11 years ago
Closed 11 years ago
Can no longer build under windows with --disable-crashreporter ('mCrashReporterMutex' : undeclared identifier)
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(firefox27- wontfix, firefox28 fixed)
RESOLVED
FIXED
mozilla28
People
(Reporter: wgianopoulos, Assigned: wgianopoulos)
References
Details
(Keywords: regression, Whiteboard: [qa-])
Attachments
(1 file)
1.02 KB,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
Windows builds specifying --disable-crashreproter fail here:
http://mxr.mozilla.org/mozilla-central/source/dom/plugins/ipc/PluginModuleParent.cpp#1564
with undeclared identifier mCrashReporterMutex.
Assignee | ||
Comment 1•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Attachment #8342329 -
Attachment description: Fix WIndows build issue → Fix Windows build issue
Assignee | ||
Updated•11 years ago
|
Summary: Can no longer build under windows with --disable-crashreporter → Can no longer build under windows with --disable-crashreporter ('mCrashReporterMutex' : undeclared identifier)
Updated•11 years ago
|
Attachment #8342329 -
Flags: review? → review?(benjamin)
Assignee | ||
Comment 2•11 years ago
|
||
Oops I thought I had requested review from bsmedberg. My Bad!
Updated•11 years ago
|
Attachment #8342329 -
Flags: review?(benjamin) → review+
Assignee | ||
Updated•11 years ago
|
Keywords: checkin-needed
Comment 3•11 years ago
|
||
Keywords: checkin-needed
Comment 4•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla28
Comment 5•11 years ago
|
||
the patch is also needed for firefox27
Assignee | ||
Comment 6•11 years ago
|
||
The patch that caused the regression has also landed on Aurora. I am not sure if that means this should be as well. It is a trivial, obvious fix, but it only impacts doing local windows builds with non-standard build options.
tracking-firefox27:
--- → ?
Comment 7•11 years ago
|
||
No need to track although if a low risk uplift would help go ahead and nominate it.
Updated•11 years ago
|
Assignee | ||
Comment 8•11 years ago
|
||
Issue here is. Do we really care? Exactly who would be building Firefox 27 with a non-standard mozconfig who would also not have the capability to apply the patch themselves?
status-firefox27:
--- → wontfix
status-firefox28:
--- → fixed
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•