Re: [gtk-osx-devel] Bison 3 and WebKit
On Dec 27, 2014, at 9:55 AM, Philip Chimento philip.chime...@gmail.com wrote: On Mon, Dec 22, 2014 at 11:28 AM, John Ralls jra...@ceridwen.us mailto:jra...@ceridwen.us wrote: On Dec 22, 2014, at 9:11 AM, Philip Chimento philip.chime...@gmail.com mailto:philip.chime...@gmail.com wrote: On Mon, Dec 22, 2014 at 9:04 AM, John Ralls jra...@ceridwen.us mailto:jra...@ceridwen.us wrote: On Dec 21, 2014, at 9:09 PM, Philip Chimento philip.chime...@gmail.com mailto:philip.chime...@gmail.com wrote: On Tue, Dec 16, 2014 at 12:39 PM, John Ralls jra...@ceridwen.us mailto:jra...@ceridwen.us wrote: On Dec 16, 2014, at 12:25 AM, Philip Chimento philip.chime...@gmail.com mailto:philip.chime...@gmail.com wrote: On Mon, Dec 15, 2014 at 11:01 AM, John Ralls jra...@ceridwen.us mailto:jra...@ceridwen.us wrote: On Dec 14, 2014, at 10:14 PM, Philip Chimento philip.chime...@gmail.com mailto:philip.chime...@gmail.com wrote: On Mon, Dec 8, 2014 at 8:15 PM, John Ralls jra...@ceridwen.us mailto:jra...@ceridwen.us wrote: On Dec 8, 2014, at 3:37 PM, Philip Chimento philip.chime...@gmail.com mailto:philip.chime...@gmail.com wrote: On Sun, Dec 7, 2014 at 5:05 PM, John Ralls jra...@ceridwen.us mailto:jra...@ceridwen.us wrote: The upgrade of Bison to version 3 which you graciously provided breaks the WebKit build, which you also graciously provided. ISTR that you mumbled something about working on building a newer WebKit version. Are you? Yes! It's been a bit pre-empted by other stuff, but I am still working on building WebKit 2.4.7. [...] [...] should I perhaps keep the old WebKit 1.x module intact, and instead add a new one for webkitgtk 2.x? I might have to add a new one anyway since webkitgtk 2.x has discontinued the old WebKit 1 single-process API, and a lot of apps still depend on it. How about two new modules named webkit1gtk and webkit2gtk? Yes, I think that would be wise. How about just “webkit” and “webkit2” so that app modulesets don’t break gratuitously? Actually what I meant was keeping the existing one, and adding two more. All the APIs and version numbers are confusing but here's everything I'm proposing in a nutshell: - WebKit - WebKitGTK 1.x, WebKit 1 API, works with GTK 2.x (could be built for GTK 3.x but let's not bother) - webkit1gtk - WebKitGTK 2.4.x, WebKit 1 API, works with GTK 3.x - webkit2gtk - WebKitGTK 2.6, WebKit 2 API, works with GTK 3.x I picked webkit2gtk because that's what the pkg-config file calls itself and webkit1gtk in analogy to that. (Actually webkit1gtk's pkg-config file is called webkitgtk so that might be better for consistency but a more confusing name.) Ah, got it. Could we use ‘webkit[12]gtk3’ to make it clear that they’re gtk3-only? That aside, the only way to deal with the confusion is to comment each module with what it’s for. Done, pull request here: https://github.com/jralls/gtk-osx-build/pull/32 https://github.com/jralls/gtk-osx-build/pull/32 Yeah, saw that, I’ll make comments on the pull request. I still get an error building libsoup, only on modulesets-unstable. I worked around it by adding --disable-introspection to libsoup's autogenargs in my local configuration file, since I assume it's a temporary problem. I haven't yet had time to pinpoint where it came from, though. Have you seen this before at all? GISCAN Soup-2.4.gir Traceback (most recent call last): File /Users/fliep/gtk/inst/bin/g-ir-scanner, line 55, in module sys.exit(scanner_main(sys.argv)) File /Users/fliep/gtk/inst/lib/gobject-introspection/giscanner/scannermain.py, line 517, in scanner_main ss = create_source_scanner(options, args) File /Users/fliep/gtk/inst/lib/gobject-introspection/giscanner/scannermain.py, line 430, in create_source_scanner ss.parse_files(filenames) File /Users/fliep/gtk/inst/lib/gobject-introspection/giscanner/sourcescanner.py, line 256, in parse_files self._parse(headers) File /Users/fliep/gtk/inst/lib/gobject-introspection/giscanner/sourcescanner.py, line 302, in _parse proc.stdin.write('#ifndef %s\n' % (define, )) IOError: [Errno 32] Broken pipe make[3]: *** [Soup-2.4.gir] Error 1 make[2]: *** [all] Error 2 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 No, but I haven’t tried building libsoup in unstable recently. Looks like a g-ir-scanner bug, though. Someone changed the format to use only one arg and screwed up by forgetting to remove the comma in the now-single-member tuple. Regards, John Ralls ___ Gtk-osx-devel-list mailing list Gtk-osx-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-osx-devel-list
Re: [gtk-osx-devel] Bison 3 and WebKit
On Mon, Dec 15, 2014 at 11:01 AM, John Ralls jra...@ceridwen.us wrote: On Dec 14, 2014, at 10:14 PM, Philip Chimento philip.chime...@gmail.com wrote: On Mon, Dec 8, 2014 at 8:15 PM, John Ralls jra...@ceridwen.us wrote: On Dec 8, 2014, at 3:37 PM, Philip Chimento philip.chime...@gmail.com wrote: On Sun, Dec 7, 2014 at 5:05 PM, John Ralls jra...@ceridwen.us wrote: The upgrade of Bison to version 3 which you graciously provided breaks the WebKit build, which you also graciously provided. ISTR that you mumbled something about working on building a newer WebKit version. Are you? Yes! It's been a bit pre-empted by other stuff, but I am still working on building WebKit 2.4.7. What is it about Bison 3 that breaks the old build? [log] Moving ~/.local/bin/bison out of the way, so that it uses the one Apple ships (v.2.3), clears the problem. I've got something almost working for modulesets-stable on the update-webkit branch of ptomato/gtk-osx-build: https://github.com/ptomato/gtk-osx-build/tree/update-webkit There's one thing left I can't figure out. The build stalls while linking libWebCoreSVG.la. ranlib prints out reams of complaints about object files having no symbols, although, that seems to be normal in itself. Then it stalls at a point where the last two are repeats of the two before that: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libWebCoreSVG.a(libWebCoreSVG_la-CachedSVGDocumentReference.o) has no symbols /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libWebCoreSVG.a(libWebCoreSVG_la-JSSVGZoomAndPan.o) has no symbols /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libWebCoreSVG.a(libWebCoreSVG_la-CachedSVGDocumentReference.o) has no symbols /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libWebCoreSVG.a(libWebCoreSVG_la-JSSVGZoomAndPan.o) has no symbols And sits there for 25 minutes, maxing out one CPU - at that point I killed it. Restarting the build completed with no problem. If you wipe the source directory and build again from scratch, it stalls again. I'm curious if anyone else has this problem. Also, if you're waiting on this module to be buildable again, I can submit a pull request that only updates modulesets-stable while I work on the other two modulesets. Does using `make -j1` change anything? I’ll pull it and give it a try later today. If all else fails we can just disable SVG. I just deleted Bison 3 after bootstrapping, so it’s not holding anything up for me. That doesn’t help anyone who needs both gstreamer and WebKit, though. Maybe bison 2.7.1 would work for both. -j1 did the trick - thank you for the suggestion! I'd rather upgrade WebKit than downgrade Bison, although 2.7.1 would work for gstreamer; it needs 2.4 or later. Best, -- Philip ___ Gtk-osx-devel-list mailing list Gtk-osx-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-osx-devel-list
Re: [gtk-osx-devel] Bison 3 and WebKit
On Dec 14, 2014, at 10:14 PM, Philip Chimento philip.chime...@gmail.com wrote: On Mon, Dec 8, 2014 at 8:15 PM, John Ralls jra...@ceridwen.us mailto:jra...@ceridwen.us wrote: On Dec 8, 2014, at 3:37 PM, Philip Chimento philip.chime...@gmail.com mailto:philip.chime...@gmail.com wrote: On Sun, Dec 7, 2014 at 5:05 PM, John Ralls jra...@ceridwen.us mailto:jra...@ceridwen.us wrote: The upgrade of Bison to version 3 which you graciously provided breaks the WebKit build, which you also graciously provided. ISTR that you mumbled something about working on building a newer WebKit version. Are you? Yes! It's been a bit pre-empted by other stuff, but I am still working on building WebKit 2.4.7. What is it about Bison 3 that breaks the old build? [log] Moving ~/.local/bin/bison out of the way, so that it uses the one Apple ships (v.2.3), clears the problem. I've got something almost working for modulesets-stable on the update-webkit branch of ptomato/gtk-osx-build: https://github.com/ptomato/gtk-osx-build/tree/update-webkit https://github.com/ptomato/gtk-osx-build/tree/update-webkit There's one thing left I can't figure out. The build stalls while linking libWebCoreSVG.la. ranlib prints out reams of complaints about object files having no symbols, although, that seems to be normal in itself. Then it stalls at a point where the last two are repeats of the two before that: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libWebCoreSVG.a(libWebCoreSVG_la-CachedSVGDocumentReference.o) has no symbols /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libWebCoreSVG.a(libWebCoreSVG_la-JSSVGZoomAndPan.o) has no symbols /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libWebCoreSVG.a(libWebCoreSVG_la-CachedSVGDocumentReference.o) has no symbols /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libWebCoreSVG.a(libWebCoreSVG_la-JSSVGZoomAndPan.o) has no symbols And sits there for 25 minutes, maxing out one CPU - at that point I killed it. Restarting the build completed with no problem. If you wipe the source directory and build again from scratch, it stalls again. I'm curious if anyone else has this problem. Also, if you're waiting on this module to be buildable again, I can submit a pull request that only updates modulesets-stable while I work on the other two modulesets. Does using `make -j1` change anything? I’ll pull it and give it a try later today. If all else fails we can just disable SVG. I just deleted Bison 3 after bootstrapping, so it’s not holding anything up for me. That doesn’t help anyone who needs both gstreamer and WebKit, though. Maybe bison 2.7.1 would work for both. Regards, John Ralls ___ Gtk-osx-devel-list mailing list Gtk-osx-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-osx-devel-list
Re: [gtk-osx-devel] Bison 3 and WebKit
On Mon, Dec 8, 2014 at 8:15 PM, John Ralls jra...@ceridwen.us wrote: On Dec 8, 2014, at 3:37 PM, Philip Chimento philip.chime...@gmail.com wrote: On Sun, Dec 7, 2014 at 5:05 PM, John Ralls jra...@ceridwen.us wrote: The upgrade of Bison to version 3 which you graciously provided breaks the WebKit build, which you also graciously provided. ISTR that you mumbled something about working on building a newer WebKit version. Are you? Yes! It's been a bit pre-empted by other stuff, but I am still working on building WebKit 2.4.7. What is it about Bison 3 that breaks the old build? [log] Moving ~/.local/bin/bison out of the way, so that it uses the one Apple ships (v.2.3), clears the problem. I've got something almost working for modulesets-stable on the update-webkit branch of ptomato/gtk-osx-build: https://github.com/ptomato/gtk-osx-build/tree/update-webkit There's one thing left I can't figure out. The build stalls while linking libWebCoreSVG.la. ranlib prints out reams of complaints about object files having no symbols, although, that seems to be normal in itself. Then it stalls at a point where the last two are repeats of the two before that: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libWebCoreSVG.a(libWebCoreSVG_la-CachedSVGDocumentReference.o) has no symbols /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libWebCoreSVG.a(libWebCoreSVG_la-JSSVGZoomAndPan.o) has no symbols /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libWebCoreSVG.a(libWebCoreSVG_la-CachedSVGDocumentReference.o) has no symbols /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: .libs/libWebCoreSVG.a(libWebCoreSVG_la-JSSVGZoomAndPan.o) has no symbols And sits there for 25 minutes, maxing out one CPU - at that point I killed it. Restarting the build completed with no problem. If you wipe the source directory and build again from scratch, it stalls again. I'm curious if anyone else has this problem. Also, if you're waiting on this module to be buildable again, I can submit a pull request that only updates modulesets-stable while I work on the other two modulesets. Best, -- Philip ___ Gtk-osx-devel-list mailing list Gtk-osx-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-osx-devel-list
Re: [gtk-osx-devel] Bison 3 and WebKit
On Sun, Dec 7, 2014 at 5:05 PM, John Ralls jra...@ceridwen.us wrote: The upgrade of Bison to version 3 which you graciously provided breaks the WebKit build, which you also graciously provided. ISTR that you mumbled something about working on building a newer WebKit version. Are you? Yes! It's been a bit pre-empted by other stuff, but I am still working on building WebKit 2.4.7. What is it about Bison 3 that breaks the old build? -- Philip ___ Gtk-osx-devel-list mailing list Gtk-osx-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-osx-devel-list