Source/WebCore/page/EventHandler.cpp was missing: #include <wtf/SetForScope.h> /var/tmp/portage/net-libs/webkit-gtk-2.34.2/work/webkitgtk-2.34.2/Source/WebCore/page/EventHandler.cpp:2928:33: error: ‘SetForScope’ was not declared in this scope 2928 | auto allowsScrollingState = SetForScope(m_currentWheelEventAllowsScrolling, processingSteps.contains(WheelEventProcessingSteps::MainThreadForScrolling)); | ^~~~~~~~~~~ Reproducible: Always
Please include the full build.log (compressed if necessary) and emerge --info.
(In reply to Sam James from comment #1) > Please include the full build.log (compressed if necessary) and emerge > --info. Really? The reporter has pinpointed the the problem(missing #include) already
Possibly not the only missing include: https://github.com/WebKit/WebKit/commit/35405c88537864e3655489b339695aa89f35886b
(In reply to Joakim Tjernlund from comment #2) > (In reply to Sam James from comment #1) > > Please include the full build.log (compressed if necessary) and emerge > > --info. > > Really? The reporter has pinpointed the the problem(missing #include) already Yes, really, because it may well have not been the only issue. I don't think jumbo source acts deterministically as we've seen in other bugs where people say they have "no idea how it compiles for anybody else". I wasn't asking to be annoying.
I've seen this myself while fighting with USE=-opengl (and given up) at one point of time, or maybe it was another instance. But haven't seen it with (now) valid USE combinations yet. Really need that build log, especially what USE flags were used to trigger this. I hadn't seen another non-unified build fixes patch to master that Stephan linked to - I grabbed things from the early October edition instead. At this point I'm not inclined to touch this further (having messed it up once already by including things that were only meant for main branch and broke 2.34 builds) without seeing a build.log and USE flag combination.
