Summary: | net-libs/webkit-gtk-1.8.0-r200 USE="-gstreamer" - DerivedSources/webkit/WebKitDOMHTMLMediaElement.cpp:149:5: error: ‘HTMLMediaElement’ is not a member of ‘WebCore’ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paweł Rumian <gorkypl> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | brendlerjg, bugzie, chainsaw, gorkypl, ted.tanberry, tetromino |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=84526 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Build log |
Description
Paweł Rumian
2012-04-16 15:20:18 UTC
In function ‘void webkit_dom_html_media_element_set_property(GObject*, guint, const GValue*, GParamSpec*)’: DerivedSources/webkit/WebKitDOMHTMLMediaElement.cpp:149:5: error: ‘HTMLMediaElement’ is not a member of ‘WebCore’ This bug is also present in net-libs/webkit-gtk-1.8.0-r300 and fails at the exact same line. (In reply to comment #0) > It initially failed earlier because of USE="-geoloc", so the build was made > with patch from bug 411955. Same issue here. Same problem here. Reported upstream at https://bugs.webkit.org/show_bug.cgi?id=84526 Changing to all platforms as it just happened to me on an x86. The patch submitted at the upstream bugreport fixed the issue for me. Praise Jupiter! I was afraid somebody was going to tell me webkit was now going to be part of systemd. (In reply to comment #7) > The patch submitted at the upstream bugreport fixed the issue for me. Thanks. Should be fixed in 1.8.1-r301 and -r201. >*webkit-gtk-1.8.1-r301 (03 May 2012) >*webkit-gtk-1.8.1-r201 (03 May 2012) > > 03 May 2012; Alexandre Rostovtsev <tetromino@gentoo.org> > +webkit-gtk-1.8.1-r201.ebuild, +webkit-gtk-1.8.1-r301.ebuild, > +files/webkit-gtk-1.8.1-CodeGeneratorGObject-properties.patch, > +files/webkit-gtk-1.8.1-tests-xvfb.patch: > Fix build failure with USE=-gstreamer (bug #412221, thanks to Paweł Rumian). Why could it not be fixed without revbump? Now lots of people with +gstreamer have to rebuild one of the biggest packages with no real reason. (In reply to comment #10) > Why could it not be fixed without revbump? Because the fix consists of a patch to webkit-gtk's code generator. A change to the code generator results in changes in over 150 .cpp files which will get compiled no matter whether you have +gstreamer or -gstreamer. So even though the change looks safe and correct, and does not appear to break anything after doing a lot of testing, it's certainly significant enough to require a revision bump. |