[Webkit-unassigned] [Bug 131584] New: Webkit can't be built with GCC
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sat Apr 12 15:12:41 PDT 2014
https://bugs.webkit.org/show_bug.cgi?id=131584
Summary: Webkit can't be built with GCC
Product: WebKit
Version: 528+ (Nightly build)
Platform: PC
OS/Version: Windows 7
Status: NEW
Severity: Normal
Priority: P2
Component: JavaScriptCore
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: lrn1986 at gmail.com
WebKit needs an engine to execute JS. Two are available - LLInt and JIT.
JIT can be built on Windows, but only with MS VC compiler (has inline assembly code that is GCC-incompatible).
When building with JIT, ld complains about undefined symbols callToNativeFunction and callToJavaScript.
LLInt can't be built on Windows, GCC complains:
../webkitgtk-2.4.0/Source/JavaScriptCore/llint/LLIntOpcode.h:59:11: error: label 'llint_throw_from_slow_path_trampoline' used but not defined
macro(llint_throw_from_slow_path_trampoline, 1) \
This, i guess, is because LLIntAssembly.h can't be generated, the asm.rb script complains:
offlineasm: No magic values found. Skipping assembly file generation.
With neither engines being available, it's impossible to build WebKit.
This affects WebKitGTK-2.3.x (confirmed with 2.3.90) and 2.4.0.
WebKitGTK-2.2.5 builds (2.2.6 is said to be buildable as well, but i haven't tried it yet).
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list