Package Details: firefox-vaapi 133.0-1

Git Clone URL: https://aur.archlinux.org/firefox-vaapi.git (read-only, click to copy)
Package Base: firefox-vaapi
Description: Fast, Private & Safe Web Browser (with VA-API patches)
Upstream URL: https://www.mozilla.org/firefox/
Keywords: firefox libva va-api vaapi video
Licenses: MPL-2.0
Conflicts: firefox
Provides: firefox
Submitter: ewout
Maintainer: dcelasun
Last Packager: dcelasun
Votes: 12
Popularity: 1.02
First Submitted: 2023-02-24 13:48 (UTC)
Last Updated: 2024-12-01 12:05 (UTC)

Required by (171)

Sources (7)

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

xzntest commented on 2024-12-05 01:19 (UTC)

Need slightly older version of rust, one that uses LLVM 18 instead of 19. Rust 1.81 should work.

Zexal commented on 2024-12-03 09:10 (UTC) (edited on 2024-12-05 17:53 (UTC) by Zexal)

133.0-1 doesn't compile. Any thoughts?

12:20.17 ld.lld: error: ../../../../../x86_64-unknown-linux-gnu/release/libbuiltins_static.a(builtins_static-9340740c376201f4.builtins_static.d4eca79a53e7550b-cgu.0.rcgu.o): Invalid attribute group entry (Producer: 'LLVM19.1.1-rust-1.83.0-stable' Reader: 'LLVM 18.1.8')

EDIT: Thanks to xzntest, realized the issue. Never use rust so I had not idea how rust toolchains are supposed to work. Uninstalled stable and installed last release with LLVM 18 (1.81.1). If its using LLVM from the rust toolchain why doesn't it just use the same LLVM at the final step? Hmm..

Anyways, copy & paste if anyone else is having the same issue (if same arch):

rustup toolchain install 1.81.0
rustup default 1.81.0-x86_64-unknown-linux-gnu
rustup toolchain uninstall stable-x86_64-unknown-linux-gnu
rustc --version --verbose

kikislater commented on 2024-11-25 04:09 (UTC)

@deemon : just comment these lines => 

161 # System libraries
162 ac_add_options --with-system-nspr
163 ac_add_options --with-system-nss

deemon commented on 2024-11-24 10:16 (UTC) (edited on 2024-11-24 10:24 (UTC) by deemon)

For me the build failed on Manjaro, because it complained that my nss is not >=3.105 or something (Manjaro has still 3.104) -- np, will wait until manjaro gets the correct version also sometime later. But it's not even listed as dependency and started building regardless and failed later, when the build process itself didn't have correct version.

kikislater commented on 2024-11-23 05:30 (UTC)

Thank you broller, this is what we need !

broller commented on 2024-11-23 04:45 (UTC)

@dcelasun Oh okay, I understand. Thank you for explaining, appreciate the clarifications a lot!

dcelasun commented on 2024-11-22 22:53 (UTC) (edited on 2024-11-22 22:53 (UTC) by dcelasun)

@broller: It would, but only if you are reusing the same build directory between versions, and only if you use makepkg --noextract with the second build onwards. Basically, it's something for individual users to do, not for me in the PKGBUILD. At most I can add a comment in the code.

broller commented on 2024-11-22 22:50 (UTC)

@dcelasun I understand and am fully aware the first build becomes a lot slower. Would it still not help speeding up compilation whenever this package gets an update, eg. from upstream firefox? That was my initial intent, sorry if I worded it wrong.

dcelasun commented on 2024-11-22 20:48 (UTC)

sccache is great for speeding up subsequent builds, but it actually slows down the first build. It's for Firefox developers who change a few lines of code and don't want to rebuild the entire thing.

This package follows the Arch PKGBUILD as closely as possible, so anyone building it in a clean chroot (i.e "the Arch way") would actually have worse performance. If this doesn't apply to you, try adding that option to anywhere in mozconfig, so maybe around line 145 and give it a shot. To use the cache, make sure your second build doesn't overwrite src/, so use makepkg --noextract.

broller commented on 2024-11-22 20:19 (UTC)

During my build of firefox, I got invited to check this link out: https://firefox-source-docs.mozilla.org/setup/configuring_build_options.html#sccache

ive taken a look at the PKGBUILD file but couldnt find any form of ac_add_options --with-ccache=sccache in the prepare() function that is recommended to speed incremental builds up.

Would it be possible to add it to the PKGBUILD or is it intentionally omitted?

1 2 3 4 5 6 .. 8 Next › Last »