| 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: | 71 |
| Popularity: | 0.76 |
| First Submitted: | 2017-06-30 07:40 (UTC) |
| Last Updated: | 2024-11-16 02:41 (UTC) |
In addition to compile time (thanks @MadMe for the tip; [here's additional info https://wiki.gentoo.org/wiki/MAKEOPTS] but this thread wrong forum to discuss), what about the download time? Been trying to download source now for about 6 hours, progress: 3.08 MB.... What's going on with the throttling (280 bytes/s)?
In light of the considerable dwonload and compile time, would you consider providing a binary (for example, with with gpg signature)?
It took me 13.5 hours on an AMD Athlon X2 (not my oldest machine). It was long but it was successful.
Sorry for offtopic, but for this time consuming package it might be worth it @tuxsavvy there is an more easy way: it is possible to set the makeflags in /etc/makepkg.conf
You find under
# ARCHITECTURE, COMPILE FLAGS MAKEFLAGS="-j1"
you can change it that way: https://wiki.archlinux.org/index.php/makepkg#MAKEFLAGS
i set it direct: MAKEFLAGS="-j9" # it should be one more than your virtual cpus
It took me ~5-6 hours on Core2Duo E8400 with 8GB RAM.
The overall default compile process does not take advantage of SMP set up. I initially ran it with the default PKGBUILD file but cancelled it about 2-3 hours in before setting it up to use 2 CPU. Check under _build area:
make all stamp-po
If it takes advantage of SMP it should be something like:
make -j 2 all stamp-po
Where 2 is however many CPU you have.
@joe1984: Quick googling brings me to an answer: too long path. [1] Could you check your path? By the way, length limitations are smaller on encrypted filesystems.
As a reference, it takes me almost 9 hours to build webkitgtk & webkitgtk2. (Linode VPS with 1G RAM + 1.5G swap)
@saligrama I cancelled it after 2 hours of compiling, and you've got a more powerful machine than I do. I may wait until I can let it run overnight. Anyone have a time-estimate on how long it has (should) take?
After a few hours of compiling, I get this error. ../webkitgtk-2.4.11/Source/WebCore/plugins/PluginView.cpp:1494:1: fatal error: opening dependency file Source/WebCore/plugins/.deps/libWebCore_la-PluginView.Tpo: No such file or directory } // namespace WebCore ^ compilation terminated. make[1]: *** [GNUmakefile:59766: Source/WebCore/plugins/libWebCore_la-PluginView.lo] Error 1
Is this taking a very long time to compile for anyone else? It has taken almost 4 hours and is still in progress. I'm running on an i7-6700HQ with 16GB of RAM.
I also found this:
patching file Source/WebCore/platform/text/enchant/TextCheckerEnchant.cpp
patch unexpectedly ends in middle of line
Hunk #1 succeeded at 128 with fuzz 1.
It's related?, or does it not matter?
I do not think so
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 FLAGSuseMAKEFLAGS="-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).