http://trac.webkit.org/changeset/143319 broke the build: Causes build issues on win32 (Requested by carewolf on #webkit). This is an automatic bug report generated by the sheriff-bot. If this bug report was created because of a flaky test, please file a bug for the flaky test (if we don't already have one on file) and dup this bug against that bug so that we can track how often these flaky tests case pain. "Only you can prevent forest fires." -- Smokey the Bear
Created attachment 189068 [details] ROLLOUT of r143319 Any committer can land this patch automatically by marking it commit-queue+. The commit-queue will build and test the patch before landing to ensure that the rollout will be successful. This process takes approximately 15 minutes. If you would like to land the rollout faster, you can use the following command: webkit-patch land-attachment ATTACHMENT_ID where ATTACHMENT_ID is the ID of this attachment.
Comment on attachment 189068 [details] ROLLOUT of r143319 Clearing flags on attachment: 189068 Committed r143323: <http://trac.webkit.org/changeset/143323>
All reviewed patches have been landed. Closing bug.
Would it be possible to know more details on the QT Windows build errors? Did they happen on release/debug? With MSVC/MinGW? Thanks.
(In reply to comment #4) > Would it be possible to know more details on the QT Windows build errors? Did they happen on release/debug? With MSVC/MinGW? > > Thanks. The issue is long solved. The only reason MathML has not been reenabled is because Chrome disabled them due to potential security issues.
(In reply to comment #5) > The issue is long solved. The only reason MathML has not been reenabled is because Chrome disabled them due to potential security issues. OK, I was trying to build WebKitQT on Windows, but I'm glad to know that I don't need to bother with that... Thanks for the info.