Bug 161477 - webkit-gtk 2.13.90 fails to build due to missing Bytecodes.h
Summary: webkit-gtk 2.13.90 fails to build due to missing Bytecodes.h
Status: RESOLVED DUPLICATE of bug 191692
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-31 23:30 PDT by Jeremy Huddleston Sequoia
Modified: 2018-11-15 12:17 PST (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeremy Huddleston Sequoia 2016-08-31 23:30:33 PDT
After addressing bug #161475, builds from the 2.13.90 tarball fail due to Bytecodes.h missing.

In file included from /opt/local/var/macports/build/_Users_jeremy_src_macports_trunk_dports_www_webkit2-gtk-devel/webkit2-gtk-devel/work/build/DerivedSources/WebCore/StyleBuilder.cpp:9:
In file included from /opt/local/var/macports/build/_Users_jeremy_src_macports_trunk_dports_www_webkit2-gtk-devel/webkit2-gtk-devel/work/webkitgtk-2.13.90/Source/WebCore/css/StyleBuilderConverter.h:51:
In file included from /opt/local/var/macports/build/_Users_jeremy_src_macports_trunk_dports_www_webkit2-gtk-devel/webkit2-gtk-devel/work/webkitgtk-2.13.90/Source/WebCore/css/StyleResolver.h:26:
In file included from /opt/local/var/macports/build/_Users_jeremy_src_macports_trunk_dports_www_webkit2-gtk-devel/webkit2-gtk-devel/work/webkitgtk-2.13.90/Source/WebCore/css/DocumentRuleSets.h:28:
In file included from /opt/local/var/macports/build/_Users_jeremy_src_macports_trunk_dports_www_webkit2-gtk-devel/webkit2-gtk-devel/work/webkitgtk-2.13.90/Source/WebCore/css/RuleSet.h:26:
In file included from /opt/local/var/macports/build/_Users_jeremy_src_macports_trunk_dports_www_webkit2-gtk-devel/webkit2-gtk-devel/work/webkitgtk-2.13.90/Source/WebCore/cssjit/SelectorCompiler.h:32:
In file included from /opt/local/var/macports/build/_Users_jeremy_src_macports_trunk_dports_www_webkit2-gtk-devel/webkit2-gtk-devel/work/build/DerivedSources/ForwardingHeaders/JavaScriptCore/MacroAssemblerCodeRef.h:1:
In file included from /opt/local/var/macports/build/_Users_jeremy_src_macports_trunk_dports_www_webkit2-gtk-devel/webkit2-gtk-devel/work/webkitgtk-2.13.90/Source/JavaScriptCore/assembler/MacroAssemblerCodeRef.h:31:
In file included from /opt/local/var/macports/build/_Users_jeremy_src_macports_trunk_dports_www_webkit2-gtk-devel/webkit2-gtk-devel/work/webkitgtk-2.13.90/Source/JavaScriptCore/llint/LLIntData.h:30:
/opt/local/var/macports/build/_Users_jeremy_src_macports_trunk_dports_www_webkit2-gtk-devel/webkit2-gtk-devel/work/webkitgtk-2.13.90/Source/JavaScriptCore/bytecode/Opcode.h:33:10: fatal error: 'Bytecodes.h' file not
      found
#include "Bytecodes.h"
         ^
1 error generated.
Comment 1 Carlos Garcia Campos 2016-08-31 23:33:23 PDT
That's autogenerated file, try running build-webkit again, there must be a problem with the dependencies in the cmake files
Comment 2 Jeremy Huddleston Sequoia 2016-08-31 23:34:08 PDT
It looks like it's supposed to be generated by JavaScriptCore but isn't.
Comment 3 Jeremy Huddleston Sequoia 2016-08-31 23:36:47 PDT
I'm rebuilding with -j1 to get a good build log to attach for the failure.  I'll attach it tomorrow.
Comment 4 Michael Catanzaro 2016-09-01 05:57:17 PDT
(In reply to comment #3)
> I'm rebuilding with -j1 to get a good build log to attach for the failure. 
> I'll attach it tomorrow.

Often bugs like these only occur during parallel builds....
Comment 5 Fujii Hironori 2016-09-01 06:58:57 PDT
Bug 157261 seems a same problem.
Comment 6 Jeremy Huddleston Sequoia 2016-09-01 09:40:47 PDT
Yeah, looks like a parallel build issue, likely due to a missing dependency.  Building with -j1 gets farther.  I'll dig into this after figuring out the rest of the issues...
Comment 7 Michael Catanzaro 2018-11-15 12:17:37 PST
Seems like a missing dependency indeed. More discussion in bug #191692. I know this bug was opened years earlier, but let's continue in the one with more discussion.

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