Bug 139588 - Building webkit-gtk >=2.6.4 Fails: Error INTPTR_MAX was not declared in this scope
Summary: Building webkit-gtk >=2.6.4 Fails: Error INTPTR_MAX was not declared in this ...
Status: RESOLVED DUPLICATE of bug 140616
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-12 09:39 PST by Rob MacKinnon
Modified: 2015-09-04 08:41 PDT (History)
2 users (show)

See Also:

Attachments
Build Log (4.76 KB, text/x-log)
2014-12-12 09:39 PST, Rob MacKinnon 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rob MacKinnon 2014-12-12 09:39:35 PST 
Created attachment 243201 [details]
Build Log

I'm no coder, but I can normally with a little google-fu solve my problems.  Building webkit-gtk 2.6.4 fails while attempting JavaScriptCore/bytcode/CodeBlock.cpp.  From what I gather from the error is it's not picking up a guarded limits.h or cstdint or stdint.h:

In file included from Source/JavaScriptCore/bytecode/CodeBlock.cpp:62:0:
Source/JavaScriptCore/runtime/TypeProfiler.h: In constructor ‘JSC::QueryKey::QueryKey(WTF::HashTableDeletedValueType)’:
Source/JavaScriptCore/runtime/TypeProfiler.h:58:22: error: ‘INTPTR_MAX’ was not declared in this scope
Source/JavaScriptCore/runtime/TypeProfiler.h: In member function ‘bool JSC::QueryKey::isHashTableDeletedValue() const’:
Source/JavaScriptCore/runtime/TypeProfiler.h:62:65: error: ‘INTPTR_MAX’ was not declared in this scope

Adding an include in TypeProfiler.h or CodeBlock.h doesn't seem to resolve the issue, but as expected directly replacing the entries of INTPTR_MAX with values in /usr/include/stdint.h allows it to magically build.
Comment 1 Pacho Ramos 2015-01-23 09:58:18 PST 
Maybe related with bug 140616
Comment 2 Michael Catanzaro 2015-09-04 08:41:40 PDT 

*** This bug has been marked as a duplicate of bug 140616 ***