Package Details: webkitgtk 3:2.4.11-27

Git Clone URL: https://aur.archlinux.org/webkitgtk.git (read-only, click to copy)
Package Base: webkitgtk
Description: Legacy Web content engine for GTK+ 3
Upstream URL: https://webkitgtk.org/
Licenses: custom
Conflicts: libwebkit3, webkitgtk3
Provides: libwebkit3, webkitgtk3
Replaces: libwebkit3, webkitgtk3
Submitter: City-busz
Maintainer: frealgagu
Last Packager: frealgagu
Votes: 70
Popularity: 0.99
First Submitted: 2017-06-30 07:40 (UTC)
Last Updated: 2023-08-15 19:11 (UTC)

Pinned Comments

frealgagu commented on 2019-04-14 18:13 (UTC) (edited on 2020-12-06 03:31 (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.webkitgtk/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 3 4 5 6 7 8 9 10 11 12 .. 16 Next › Last »

PhotonX commented on 2018-10-12 17:36 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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?

silly commented on 2018-10-08 13:33 (UTC)

@yan12125 seems to work now. thanks!

yan12125 commented on 2018-10-08 12:56 (UTC)

The build issue should have been fixed. Feel free to open a new issue at https://gitlab.com/yan12125/aur if this package is still broken.

silly commented on 2018-10-08 06:46 (UTC) (edited on 2018-10-08 06:48 (UTC) by silly)

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().
Aborting...

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 (UTC)

necklace: thanks for the suggestion. I commited your changes to https://github.com/archlinuxcn/repo/commit/eeda4dab33b926ff0ba6185d5e7b692875b2ab0f. 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 (UTC)

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.