Package Details: servo-git 0.0.1.r16.g76bb1c8-1

Git Clone URL: https://aur.archlinux.org/servo-git.git (read-only, click to copy)
Package Base: servo-git
Description: Parallel Browser Project: web browser written in Rust
Upstream URL: https://github.com/servo/servo
Keywords: browser engine rust
Licenses: MPL
Conflicts: servo
Provides: servo
Submitter: None
Maintainer: alerque (farseerfc, yar)
Last Packager: alerque
Votes: 50
Popularity: 1.03
First Submitted: 2013-08-16 05:23 (UTC)
Last Updated: 2025-10-20 17:11 (UTC)

Dependencies (26)

Required by (0)

Sources (1)

Latest Comments

1 2 3 4 5 6 7 Next › Last »

alerque commented on 2026-03-05 08:46 (UTC) (edited on 2026-03-05 09:35 (UTC) by alerque)

Yes, the tagged 0.0.5 also did not build. If anybody figures out what the build incantation is to fix this I'm open to contributions. Mention it here or PR this GH repo if you find the fix.

It seems likely related to the glibc bump Arch saw recently, and it look like it will probably come down to this upstream dependency issue.

shadow_absorber commented on 2026-02-19 13:11 (UTC)

Ello

servo-git has failed to build while being installed from paru for the last week or so

it fails on compiling the

error: failed to run custom build command for `glslopt v0.1.12`

with a huge list of output around said error

HurricanePootis commented on 2024-06-28 19:39 (UTC) (edited on 2024-06-28 21:16 (UTC) by HurricanePootis)

Hello this package needs some updates:

  1. License is not SDPX compliant; needs to be changed to MPL-2.0
  2. cargo-nightly instead of cargo. Servo has a rust-toolchain.toml file, which specifies a specific version of rust. To use that, cargo-nightly will install rustup. In addition, the export RUSTUP_TOOLCHAIN=stable needs to be commented out for rust-toolchain.toml to be used.
  3. Disable LTO. Currently, building with LTO enabled results in an error. I tried using lld, export CFLAGS+=" -ffat-lto-objects, and export CXXFLAGS+=" -ffat-lto-objects"—none of them worked.
  4. Autoconf2.13 is no longer needed.

Here is a patch file for the PKGBUILD:

diff --git a/PKGBUILD b/PKGBUILD
index 9000d6c..2c373f8 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,12 +4,12 @@
 # Contributor: beatgammit

 pkgname=servo-git
-pkgver=r47479.92196d985dc
+pkgver=r48603.3a0f5649161
 pkgrel=1
 pkgdesc='Parallel Browser Project: web browser written in Rust'
 arch=(x86_64 i686)
 url=https://github.com/servo/servo
-license=(MPL)
+license=(MPL-2.0)
 depends=(bzip2
          fontconfig
          freetype2
@@ -25,8 +25,7 @@ depends=(bzip2
          ttf-font
          xcb-util)
 install="$pkgname.install"
-makedepends=(autoconf2.13
-             cargo
+makedepends=(cargo-nightly
              clang
              cmake
              curl
@@ -41,6 +40,7 @@ provides=("${pkgname%-git}")
 conflicts=("${pkgname%-git}")
 backup=("etc/profile.d/${pkgname%-git}".{csh,sh})
 source=("$pkgname::git+$url.git")
+options=("!lto")
 sha256sums=('SKIP')

 pkgver() {
@@ -56,7 +56,7 @@ prepare() {

 build() {
    cd "$pkgname"
-   export RUSTUP_TOOLCHAIN=stable
+   #export RUSTUP_TOOLCHAIN=stable
    export CARGO_TARGET_DIR=target
    ./mach build --release
 }

micwoj92 commented on 2024-06-02 14:52 (UTC)

I have working pkgbuild.

ccicnce113424 commented on 2024-04-22 12:18 (UTC)

https://github.com/servo/servo/issues/30886#issuecomment-2053977417

cypa commented on 2024-04-10 16:30 (UTC) (edited on 2024-04-10 16:39 (UTC) by cypa)

confirm crown -vV error

error: could not execute process 'crown -vV' (never executed)

Caused by:
  No such file or directory (os error 2)
Failed in 0:00:00
[Warning] Could not generate notification: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable

I guess we need setup proper environment ...

xiota commented on 2024-01-18 19:11 (UTC)

Clean chroot. Same crown -vV error. Unfortunately, I don't know how to fix.

alerque commented on 2024-01-11 09:33 (UTC)

@xiota Happy to accept contributions. Upstream has been messing around with the build system(s) and keep adding and removing stuff. If you have patches that work to make this build at any given point feel free to post them here or ever better PR them here.

xiota commented on 2023-09-25 05:42 (UTC) (edited on 2023-12-24 19:22 (UTC) by xiota)

Clean chroot. Fails to build.

Error from 2023-12-24:

error: could not execute process `crown -vV` (never executed)

Caused by:
  No such file or directory (os error 2)
Failed in 0:00:12
[Warning] Could not generate notification: org.freedesktop.DBus.Error.NotSupported: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead

Error from 2023-09-25:

error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/home/main-builder/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc - --crate-name ___ --print=file-names -Zgcc-ld=lld --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 1)
  --- stderr
  error: the option `Z` is only accepted on the nightly compiler

  note: selecting a toolchain with `+toolchain` arguments require a rustup proxy; see <https://rust-lang.github.io/rustup/concepts/index.html>

  help: consider switching to a nightly toolchain: `rustup default nightly`

  note: for more information about Rust's stability policy, see <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html#unstable-features>

Failed in 0:00:06
[Warning] Could not generate notification: org.freedesktop.DBus.Error.NotSupported: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead

alerque commented on 2021-09-21 17:10 (UTC)

@mble It looks like the Arch [community] package for python-blessings is newer than this build demands. Probably the thing to do is patch the servo sources to be more accepting of other versions, then if it doesn't build with 1.7.x submit a patch to servo upstream to fix it. I'm happy to accept such a patch (either in comments with git format-patch or as a PR on this repository) but I'm unlikely to have time to hack around on this build any time too soon. Also either way this should be reported upstream.

1 2 3 4 5 6 7 Next › Last »