Closed
Bug 1757415
Opened 3 years ago
Closed 3 years ago
ContentEventHandler.cpp(665,22): error: expected unqualified-id "nsGkAtoms::small" bustage
Categories
(Core :: DOM: Events, defect)
Core
DOM: Events
Tracking
()
RESOLVED
FIXED
99 Branch
| Tracking | Status | |
|---|---|---|
| firefox99 | --- | fixed |
People
(Reporter: RyanVM, Assigned: RyanVM)
Details
Attachments
(1 file)
I started hitting this bustage in my local builds today, presumably due to changes in unified boundaries moving things around enough to hit it.
In file included from Unified_cpp_dom_events0.cpp:83:
C:/Users/Ryan/repos/mozilla/dom/events/ContentEventHandler.cpp(665,22): error: expected unqualified-id
nsGkAtoms::small, nsGkAtoms::span, nsGkAtoms::strike,
^
C:/PROGRA~2/WI3CF2~1/10/include/10.0.22000.0/shared/rpcndr.h(190,15): note: expanded from macro 'small'
#define small char
^
dom/file/uri
1 error generated.
We've worked around this bustage previously by undeffing small as needed and that appears to work here as well.
| Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Attachment #9265735 -
Attachment description: Bug 1757415 - Undef small in ContentEventHandler.h to avoid conflicting with the definition in rpcndr.h from the Windows SDK. → Bug 1757415 - Undef small in ContentEventHandler.h to avoid conflicting with the definition in rpcndr.h from the Windows SDK. r=smaug
Updated•3 years ago
|
Attachment #9265735 -
Attachment description: Bug 1757415 - Undef small in ContentEventHandler.h to avoid conflicting with the definition in rpcndr.h from the Windows SDK. r=smaug → Bug 1757415 - Undef small in ContentEventHandler.cpp to avoid conflicting with the definition in rpcndr.h from the Windows SDK. r=smaug
Pushed by rvandermeulen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/92b8d062ecba
Undef small in ContentEventHandler.cpp to avoid conflicting with the definition in rpcndr.h from the Windows SDK. r=smaug
Comment 3•3 years ago
|
||
Hmm, sounds like that nsGkAtoms::small should be renamed to nsGkAtoms::_small or something rather than adding #undef in each user...
Comment 4•3 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox99:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
Comment 5•3 years ago
|
||
Possibly. If this issue happens just once, undef should be fine.
You need to log in
before you can comment on or make changes to this bug.
Description
•