Closed
Bug 785679
Opened 12 years ago
Closed 12 years ago
media/gfx push required a clobber
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Assigned: glandium)
References
(Blocks 1 open bug)
Details
Much as I would have liked it if the last blocker about having to clobber every few pushes would have solved all our problems, it didn't.
https://hg.mozilla.org/integration/mozilla-inbound/rev/f26d6c5a2d93 failed in opt and debug Linux64 mochitest-1 and reftests in https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=f26d6c5a2d93 and debug Linux64 in https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=b8893f7f80c5 before starting to pass. I retriggered the builds on its landing push after clobbering, but I already know what the results will be, the clobber will have "fixed" it.
Assignee | ||
Comment 1•12 years ago
|
||
This should be fixed by the backout of bug 781529.
When building nsCanvasRenderingContext2D.cpp with -MMD, the .deps/nsCanvasRenderingContext2D.o.pp file doesn't contain a reference to ImageContainer.h. With -MD it does. AFAICT, ImageContainer.h is never declared as a system header, so this likely is a GCC bug.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → mh+mozilla
Comment 2•12 years ago
|
||
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•