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 8 ... Next › Last »

silly commented on 2018-10-08 13:33

@yan12125 seems to work now. thanks!

yan12125 commented on 2018-10-08 12:56

The build issue should have been fixed. Feel free to open a new issue at if this package is still broken.

silly commented on 2018-10-08 06:46

Confirming @Cysioland.

CDPATH="${ZSH_VERSION+.}:" && cd ../webkitgtk-2.4.11 && aclocal-1.15 -I Source/autotools
/bin/sh: aclocal-1.15: command not found
make: *** [GNUmakefile:25873: ../webkitgtk-2.4.11/aclocal.m4] Error 127
==> ERROR: A failure occurred in build().

Error while building, hardcorded to aclocal-1.15 while Arch is now on 1.16 (see below). Either it is a bug upstream to have it hardcoded. Or this needs to depend on older version of automake which feels just wrong.

pacman -Qo $(which aclocal)
/usr/bin/aclocal is owned by automake 1.16.1-1

yan12125 commented on 2018-10-07 12:45

necklace: thanks for the suggestion. I commited your changes to I'll sync that change to AUR if our build server is fine with that.

Regarding the build issue: I've tried the build a few days ago and got no issues. Could you paste the command and the full log?

And by the way, don't mark packages as outdated for (possibly) broken packages. Leave comments instead.

necklace commented on 2018-10-07 11:24

Instead of

  mkdir build-gtk{,2} path
  ln -s /usr/bin/python2 path/python

You should do

  mkdir -p build-gtk{,2} path
  ln -f -s /usr/bin/python2 path/python

So makepkg can be rerun without having to clean up anything.

yan12125 commented on 2018-10-05 12:00

@Cysioland: Make sure you build this package in clean chroots. If the package is still broken, paste full logs.

Cysioland commented on 2018-10-05 11:14

aclocal-1.15 not found

yan12125 commented on 2018-09-20 04:21

@rpodgorny: see Q6 & A6 of the updated FAQ

rpodgorny commented on 2018-09-19 16:20

isn't this a duplicate (and outdated) package to ?

yan12125 commented on 2018-08-18 12:35

@bsulyok: you may want to check Q3 of FAQ for how to reduce the build time.