Package Details: webkitgtk2 3:2.4.11-27

Git Clone URL: https://aur.archlinux.org/webkitgtk2.git (read-only, click to copy)
Package Base: webkitgtk2
Description: Legacy Web content engine for GTK+ 2
Upstream URL: https://webkitgtk.org/
Licenses: custom
Conflicts: libwebkit
Provides: libwebkit
Replaces: libwebkit
Submitter: frealgagu
Maintainer: frealgagu
Last Packager: frealgagu
Votes: 8
Popularity: 0.000000
First Submitted: 2018-12-21 02:29 (UTC)
Last Updated: 2023-08-15 19:15 (UTC)

Pinned Comments

frealgagu commented on 2019-04-14 18:31 (UTC) (edited on 2020-12-06 03:30 (UTC) by frealgagu)

FAQ

Q: What's the difference between this package and extra/webkit2gtk?

A: webkitgtk/webkitgtk2 provides WebKit1 API/ABI, which is not compatible with WebKit2 API/ABI provided by extra/webkit2gtk. WebKitGTK+ 2.4.x is the latest branch that provides WebKit1 API. Later branches provides WebKit2 API only.

Please don't flag it as out-of-date.

Q: Are there binaries for this package somewhere?

A: I maintain the latest built package at https://github.com/frealgagu/archlinux.webkitgtk2/releases

Q: "error while loading shared libraries: libicui18n.so.62: cannot open shared object file: No such file or directory"

A: You'll need to rebuild against the latest version of ICU.

Q: "error: ‘WTF::StringImpl::StaticASCIILiteraicASCIILiteral’ has not been declared" or any enchant errors.

A: If you are building in parallel, try disabling parallel using -j1 in /etc/makepkg.conf

Q: Why building takes too long time?

A: WebKit is inherently big and complex. You can modify /etc/makepkg.conf or PKGBUILD directly to build it in parallel.

  • Change "make all stamp-po" by "make -j x all stamp-po" in PKGBUILD replacing x by cores your machine has. (Thanks to @MadMe)

  • Change /etc/makepkg.conf in that way: https://wiki.archlinux.org/index.php/makepkg#Parallel_compilation under # ARCHITECTURE, COMPILE FLAGS use MAKEFLAGS="-j9" # It should be one more than your virtual CPUs. (Thanks to @tuxsavvy).

However be pending if errors occur as mentioned in previous question.

Q: How much I want to wait to a successful compilation?

A: It varies of your PC's processor and RAM, the times shared in the comments are as follow:

  • 3.5 hours to build on core i5 laptop with 8G of RAM, makeflags j4. (@cabbage)

  • 13.5 hours to build on AMD Athlon X2, makeflags j1 (@Bonnietwin).

  • 5-6 hours on Core2Duo E8400 with 8GB RAM, makeflags j2 (tuxsavvy).

  • 50 minutes on 6c/12t 3.3GHz (@kubrick).

Latest Comments

« First ‹ Previous 1 2

frealgagu commented on 2020-12-10 17:54 (UTC)

@neoresin sure, the package I've uploaded to https://github.com/frealgagu/archlinux.webkitgtk2/releases was built in a clean chroot. The pkgrel 20 contains the patch to fix the CSSGrammar.hpp bug, so you shouldn't have issues in compilation.

neoresin commented on 2020-12-10 04:25 (UTC)

@frealgagu Unfortunately still getting the error below (fatal error: CSSGrammar.hpp: No such file or directory). Any luck getting it to compile under chroot?

frealgagu commented on 2020-11-09 19:52 (UTC)

@philo I'm not longer maintaining the packages in https://cdn.repo.archlinuxcn.org so there is no a place to keep the binaries anymore.

@neoresin I'm trying to compile this version in chroot and I'll let you know

philo commented on 2020-10-22 13:24 (UTC)

Maintainer is AWOL?

neoresin commented on 2020-10-19 02:38 (UTC)

@frealgagu

Getting: 

/usr/include/glib-2.0/glib/gtypes.h:547:8: note: declared here
  547 | struct _GTimeVal
      |        ^~~~~~~~~
  CXX      DerivedSources/WebCore/libWebCore_la-InspectorWebBackendDispatchers.lo
  CXX      DerivedSources/WebCore/libWebCore_la-InspectorWebFrontendDispatchers.lo
  CXX      DerivedSources/WebCore/libWebCore_la-InspectorWebTypeBuilders.lo
DerivedSources/WebCore/CSSGrammar.cpp:160:10: fatal error: CSSGrammar.hpp: No such file or directory
  160 | #include "CSSGrammar.hpp"
      |          ^~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [GNUmakefile:66115: DerivedSources/WebCore/libWebCore_la-CSSGrammar.lo] Error 1
Tried this to no avail: https://aur.archlinux.org/packages/webkitgtk/#comment-769092 Any ideas?

philo commented on 2020-09-17 18:55 (UTC) (edited on 2020-10-24 18:57 (UTC) by philo)

@frealgagu

Contrary to what you advertise, the built package was yanked from archlinuxcn. Any reason?

EDIT- I found this link to the archcn package:

https://archlinux.pkgs.org/rolling/archlinuxcn-x86_64/webkitgtk2-3:2.4.11-19-x86_64.pkg.tar.zst.html

but there is no download link.

frealgagu commented on 2019-04-14 18:31 (UTC) (edited on 2020-12-06 03:30 (UTC) by frealgagu)

FAQ

Q: What's the difference between this package and extra/webkit2gtk?

A: webkitgtk/webkitgtk2 provides WebKit1 API/ABI, which is not compatible with WebKit2 API/ABI provided by extra/webkit2gtk. WebKitGTK+ 2.4.x is the latest branch that provides WebKit1 API. Later branches provides WebKit2 API only.

Please don't flag it as out-of-date.

Q: Are there binaries for this package somewhere?

A: I maintain the latest built package at https://github.com/frealgagu/archlinux.webkitgtk2/releases

Q: "error while loading shared libraries: libicui18n.so.62: cannot open shared object file: No such file or directory"

A: You'll need to rebuild against the latest version of ICU.

Q: "error: ‘WTF::StringImpl::StaticASCIILiteraicASCIILiteral’ has not been declared" or any enchant errors.

A: If you are building in parallel, try disabling parallel using -j1 in /etc/makepkg.conf

Q: Why building takes too long time?

A: WebKit is inherently big and complex. You can modify /etc/makepkg.conf or PKGBUILD directly to build it in parallel.

  • Change "make all stamp-po" by "make -j x all stamp-po" in PKGBUILD replacing x by cores your machine has. (Thanks to @MadMe)

  • Change /etc/makepkg.conf in that way: https://wiki.archlinux.org/index.php/makepkg#Parallel_compilation under # ARCHITECTURE, COMPILE FLAGS use MAKEFLAGS="-j9" # It should be one more than your virtual CPUs. (Thanks to @tuxsavvy).

However be pending if errors occur as mentioned in previous question.

Q: How much I want to wait to a successful compilation?

A: It varies of your PC's processor and RAM, the times shared in the comments are as follow:

  • 3.5 hours to build on core i5 laptop with 8G of RAM, makeflags j4. (@cabbage)

  • 13.5 hours to build on AMD Athlon X2, makeflags j1 (@Bonnietwin).

  • 5-6 hours on Core2Duo E8400 with 8GB RAM, makeflags j2 (tuxsavvy).

  • 50 minutes on 6c/12t 3.3GHz (@kubrick).

« First ‹ Previous 1 2