These calls were guarded with BUILDING_ON_TIGER in http://trac.webkit.org/changeset/55054 but they are required on Android too.
Created attachment 56595 [details] Patch
Comment on attachment 56595 [details] Patch I would appreciate a more detailed explanation of the change. How is this a build fix? Why are these calls required? I'm going to say r=me since this helps Android, but it's a deprecated code path, so an explanation of why it's needed (and when it can be finally removed) would help a lot.
Thanks for the review Alexey. > I would appreciate a more detailed explanation of the change. How is this a > build fix? Android has always used this code path, so adding the BUILDING_ON_TIGER guards broke the Android build. The android port is not yet fully upstreamed and we don't sync WebKit too frequently, so it took us a while to notice the break. > Why are these calls required? I'm not sure. I'm not too familiar with this code, but have filed Bug 39476 to track this. I'll land the patch now so as to fix the build, but with an additional comment about the need to avoid the use of this deprecated code path.
Comment on attachment 56595 [details] Patch Landed manually as http://trac.webkit.org/changeset/59918
Closing bug as resolved fixed.
But how does this missing block of code break the build? I would understand if it broke behavior, but I don't understand breaking the build. How did the compiler complain?
(In reply to comment #6) > But how does this missing block of code break the build? I would understand if > it broke behavior, but I don't understand breaking the build. How did the > compiler complain? Sorry, 'build' was misleading. Removing this code block caused LayoutTestController to stop working, so lots of the LayoutTests started failing.