126329 2013-12-30 22:16:33 -0800 JavaScriptCore/JSCallbackFunction.h is missing in tarball 2015-05-10 14:08:36 -0700 1 1 1 Unclassified WebKit WebKitGTK 528+ (Nightly build) Unspecified Unspecified RESOLVED FIXED P2 Normal --- 126492 1 jeremyhu webkit-unassigned berto cgarcia mcatanzaro oldest_to_newest 963460 0 jeremyhu 2013-12-30 22:16:33 -0800 The webkit-gtk tarball is missing JavaScriptCore/JSCallbackFunction.h which causes the build to fail. This is the case with 2.2.2 and 2.2.3 In file included from Source/JavaScriptCore/runtime/JSGlobalObject.cpp:83: ./Source/JavaScriptCore/API/ObjCCallbackFunction.h:32:9: fatal error: 'JavaScriptCore/JSCallbackFunction.h' file not found #import <JavaScriptCore/JSCallbackFunction.h> ^ To work around this, we're setting JSC_OBJC_API_ENABLED 0 964178 1 berto 2014-01-03 10:58:12 -0800 (In reply to comment #0) > The webkit-gtk tarball is missing > JavaScriptCore/JSCallbackFunction.h which causes the build to fail. > This is the case with 2.2.2 and 2.2.3 That file is actually in the tarball (as JavaScriptCore/API/JSCallbackFunction.h), but it looks like the forwarding header is not being generated in your case. 964187 2 jeremyhu 2014-01-03 11:17:53 -0800 (In reply to comment #1) > (In reply to comment #0) > > The webkit-gtk tarball is missing > > JavaScriptCore/JSCallbackFunction.h which causes the build to fail. > > This is the case with 2.2.2 and 2.2.3 > > That file is actually in the tarball (as > JavaScriptCore/API/JSCallbackFunction.h), but it looks like the forwarding > header is not being generated in your case. Yes, Source/JavaScriptCore/API/JSCallbackFunction.h is present, but there is no JavaScriptCore/JSCallbackFunction.h. Where is it supposed to be generated from? I'll try to debug that. 964302 3 berto 2014-01-03 15:58:19 -0800 (In reply to comment #2) > there is no JavaScriptCore/JSCallbackFunction.h. > Where is it supposed to be generated from? I'll try to debug that. That should be generate-forwarding-headers.pl 1093573 4 mcatanzaro 2015-05-10 14:08:36 -0700 I believe this issue is obsolete based on comments in bug #126492. If this issue is still present in 2.8.1 or 2.9.1 please leave a note so we can reopen.