Package Details: webkitgtk 3:2.4.11-19

Git Clone URL: (read-only, click to copy)
Package Base: webkitgtk
Description: Legacy Web content engine for GTK+ 3
Upstream URL:
Licenses: custom
Conflicts: libwebkit3, webkitgtk3
Provides: libwebkit3=2.4.11, webkitgtk3=2.4.11
Replaces: libwebkit3, webkitgtk3
Submitter: City-busz
Maintainer: frealgagu
Last Packager: frealgagu
Votes: 62
Popularity: 0.29
First Submitted: 2017-06-30 07:40
Last Updated: 2020-06-10 14:13

Sources (5)

Pinned Comments

frealgagu commented on 2019-04-14 18:13


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: We maintain built and signed packages at

Q: "error while loading shared libraries: 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: 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 3 4 5 6 7 ... Next › Last »

frealgagu commented on 2018-12-07 03:12

What do you think about split the packages and create a PKGBUILD for each one?

yan12125 commented on 2018-12-01 01:42

Dropped as I don't need this anymore.

yan12125 commented on 2018-11-10 02:27

You don't need icu62. You NEED to rebuild webkitgtk against icu 63.

philo commented on 2018-11-08 15:12

An AUR package of 'icu62 62.1-1' was released on 2018-11-05.

yan12125 commented on 2018-10-13 00:24

As I mentioned in FAQ, I maintain prebuilt and signed packages at

PhotonX commented on 2018-10-12 17:36

Sorry for the late reply and excuse my ignorance in case I am missing something obvious, but which signatures do you refer to? AUR packages are not signed, are they?

yan12125 commented on 2018-10-10 12:21

Primarily because people might get signature mismatch errors if you change a package without bumping pkgver/pkgrel.

PhotonX commented on 2018-10-10 09:41

Hmm, why not? :) You can add "-f" to the makepkg call or is the problem somewhere else?

yan12125 commented on 2018-10-10 08:24

Sorry for frequent version bumps recently. My build scripts do not build a package again without changing pkgver/pkgrel.

PhotonX commented on 2018-10-10 06:52

Would it be possible to make silent updates when fixing building problems, such that users who already have the package installed aren't forced to recompile it during the update?