Package Details: servo-git r48452.2ca6c4b52be-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: 46
Popularity: 0.113411
First Submitted: 2013-08-16 05:23 (UTC)
Last Updated: 2024-08-03 09:45 (UTC)

Dependencies (25)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

D101101 commented on 2016-01-22 06:02 (UTC)

Why does this package conflicts with 'rust' package? Why some libraries are located in /usr/lib, if you use the /opt? Isn't it better to place all library in opt directory?

celilo commented on 2015-10-22 21:54 (UTC)

Fails to build. It looks like mozjs is not building correctly. Errors below: Compiling websocket v0.12.2 Compiling webdriver v0.3.1 (https://github.com/jgraham/webdriver-rust.git#e6aac905) Compiling layers v0.1.0 (https://github.com/servo/rust-layers#5af8c6bb) Compiling gfx_traits v0.0.1 (file:///tmp/yaourt-tmp-kurtm/aur-servo-git/src/servo/components/servo) Compiling image v0.4.0 failed to run custom build command for `mozjs_sys v0.0.0 (https://github.com/servo/mozjs#74e7e954)` Process didn't exit successfully: `/tmp/yaourt-tmp-kurtm/aur-servo-git/src/servo/target/debug/build/mozjs_sys-e411d274df144795/build-script-build` (exit code: 101) --- stdout cd /tmp/yaourt-tmp-kurtm/aur-servo-git/src/servo/target/debug/build/mozjs_sys-e411d274df144795/out && \ MOZ_TOOLS="" CC="gcc" CPP="gcc -E" CXX="g++" AR="ar" \ /tmp/yaourt-tmp-kurtm/aur-servo-git/src/servo/.cargo/git/checkouts/mozjs-06d7f04b6dbb8a8e/master/mozjs/js/src/configure --enable-gczeal --disable-jemalloc creating cache ./config.cache checking Then eventually: make[3]: *** [js/src/target] Error 2 make[2]: *** [compile] Error 2 make[1]: *** [default] Error 2 make: *** [all] Error 2 thread '<main>' panicked at 'assertion failed: result.success()', /tmp/yaourt-tmp-kurtm/aur-servo-git/src/servo/.cargo/git/checkouts/mozjs-06d7f04b6dbb8a8e/master/build.rs:16 Build comake[3]: *** [js/src/target] Error 2 make[2]: *** [compile] Error 2 make[1]: *** [default] Error 2 make: *** [all] Error 2 thread '<main>' panicked at 'assertion failed: result.success()', /tmp/yaourt-tmp-kurtm/aur-servo-git/src/servo/.cargo/git/checkouts/mozjs-06d7f04b6dbb8a8e/master/build.rs:16 Build make[3]: *** [js/src/target] Error 2 make[2]: *** [compile] Error 2 make[1]: *** [default] Error 2 make: *** [all] Error 2 thread '<main>' panicked at 'assertion failed: result.success()', /tmp/yaourt-tmp-kurtm/aur-servo-git/src/servo/.cargo/git/checkouts/mozjs-06d7f04b6dbb8a8e/master/build.rs:16 Build completed in 2009.22s ==> ERROR: A failure occurred in build(). Aborting... completed in 2009.22s ==> ERROR: A failure occurred in build(). Aborting... mpleted in 2009.22s ==> ERROR: A failure occurred in build(). Aborting...

emw commented on 2015-08-16 08:40 (UTC)

Hi, I had problems installing today, namely the following message: install: cannot stat ‘/tmp/yaourt-tmp-emw/aur-servo-git/src/servo/components/servo/target/debug/servo’: No such file or directory It seems like the build products have moved. When I ran `ln -s ../../target .` in /tmp/yaourt-tmp-emw/aur-servo-git/src/servo/components/servo and restarted building, all worked well.

skgsergio commented on 2015-08-15 14:46 (UTC)

Yes it can be avoided. If you create a .servobuild file in the root directory of the git project you use your system rust and cargo: https://github.com/servo/servo/blob/master/servobuild.example#L16-L24

klusark commented on 2015-06-08 23:48 (UTC)

@bb010g, I don't think so. Servo ships it's own version of rust, so we need the rust libraries. I'll see if I can resolve the conflict though.

bb010g commented on 2015-06-07 21:21 (UTC)

Is there anyway the conflict with `rust` could be avoided?

rvalles commented on 2015-05-30 12:37 (UTC)

Forgot to say, trivial change does the trick: ./mach build -d

rvalles commented on 2015-05-30 12:35 (UTC)

Silly issue today: :: Checking servo-git integrity... ==> Making package: servo-git 8255.ccf5f96-1 (Sat May 30 12:35:26 UTC 2015) ==> Retrieving sources... -> Updating servo git repo... Fetching origin ==> Validating source files with md5sums... servo ... Skipped :: Building servo-git package(s)... ==> Making package: servo-git 10607.99b79fc-1 (Sat May 30 12:35:29 UTC 2015) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Updating servo git repo... Fetching origin ==> Validating source files with md5sums... servo ... Skipped ==> Extracting sources... -> Creating working copy of servo git repo... Reset branch 'makepkg' ==> Starting pkgver()... ==> Removing existing $pkgdir/ directory... ==> Starting build()... Please specify either --dev (-d) for a development build, or --release (-r) for an optimized build. ==> ERROR: A failure occurred in build(). Aborting... :: servo-git cleaning skipped :: failed to build servo-git package(s)

KenjiTakahashi commented on 2015-05-04 22:22 (UTC)

Please disregard, it was a configuration problem on my side... The package works fine.

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »