Package Details: waterfox-classic-git 56.3+4e300fc5cebf-2

Git Clone URL: https://aur.archlinux.org/waterfox-classic-git.git (read-only)
Package Base: waterfox-classic-git
Description: 64-Bit optimized Firefox fork, no data collection, allows unsigned extensions
Upstream URL: https://www.waterfoxproject.org/
Licenses: MPL
Conflicts: waterfox, waterfox-bin, waterfox-git
Provides: waterfox=56.3+4e300fc5cebf
Submitter: ilikenwf
Maintainer: ilikenwf
Last Packager: ilikenwf
Votes: 9
Popularity: 0.006174
First Submitted: 2019-10-09 17:32
Last Updated: 2019-10-09 19:02

Dependencies (32)

Required by (0)

Sources (4)

Latest Comments

1 2 3 4 Next › Last »

toxygen commented on 2019-11-14 15:32

i use waterfox-classic-kpe and i have the same problems with rust/llvm

versions that work for me are

clang 8.0.1-1

llvm 8.0.1-3

llvm-libs 8.0.1-3

compiler-rt 8.0.1-1

rust 1:1.38.0-1.1

EojjN commented on 2019-11-11 20:14

OK, I'm just downgrading Rust now so we'll see if that works out. I guess the newest version isn't always the most stable but who knows why they use an old version.

I tried removing the rust-simd option from mozconfig too, btw, but it didn't work.

ilikenwf commented on 2019-11-11 20:10

Looks like it to me - Arch updates rust more often than the Mozillans it seems, which is funny to consider since Mozilla runs Rust...

But 1.1.37, I bet, or 1.1.36 should let you build.

EojjN commented on 2019-11-11 18:48

Is there just one issue here then? I wasn't sure if the error after "2." was just a reference to the earlier one.

ilikenwf commented on 2019-11-11 18:19

@EojjN I haven't had a chance to figure this one out yet, but suspect the current version of Rust arch is using is too new.

For waterfox-current-git I already had to force a downgrade of rust by one version.

If you could try editing the mozconfig to remove the rust-simd option, it may build. If not you may want to install downgrade and test building with rust 1.1.37 or 1.1.38 instead of the current 1.1.39.

Optionally you can also mention this in a new issue on the tracker, so Alex can fix it.

EojjN commented on 2019-11-11 18:16

Hi there,

I've just tried to compile this package using yay but it has failed with the following errors

1.

error: use of deprecated item 'try': use the ? operator instead --> /home/aj/.cache/yay/waterfox-classic-git/src/Waterfox/xpcom/rust/nsstring/src/lib.rs:138:5 | 138 | / bitflags! { 139 | | // While this has the same layout as u16, it cannot be passed 140 | | // over FFI safely as a u16. 141 | | #[repr(C)] ... | 149 | | } 150 | | } | |_____^ | note: lint level defined here --> /home/aj/.cache/yay/waterfox-classic-git/src/Waterfox/xpcom/rust/nsstring/src/lib.rs:116:9 | 116 | #![deny(warnings)] | ^^^^^^^^ = note: #[deny(deprecated)] implied by #[deny(warnings)] = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error: use of deprecated item 'try': use the ? operator instead --> /home/aj/.cache/yay/waterfox-classic-git/src/Waterfox/xpcom/rust/nsstring/src/lib.rs:138:5 | 138 | / bitflags! { 139 | | // While this has the same layout as u16, it cannot be passed 140 | | // over FFI safely as a u16. 141 | | #[repr(C)] ... | 149 | | } 150 | | } | |_____^ | = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error: use of deprecated item 'try': use the ? operator instead --> /home/aj/.cache/yay/waterfox-classic-git/src/Waterfox/xpcom/rust/nsstring/src/lib.rs:154:5 | 154 | / bitflags! { 155 | | // While this has the same layout as u16, it cannot be passed 156 | | // over FFI safely as a u16. 157 | | #[repr(C)] ... | 161 | | } 162 | | } | |_____^ | = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error: use of deprecated item 'try': use the ? operator instead --> /home/aj/.cache/yay/waterfox-classic-git/src/Waterfox/xpcom/rust/nsstring/src/lib.rs:154:5 | 154 | / bitflags! { 155 | | // While this has the same layout as u16, it cannot be passed 156 | | // over FFI safely as a u16. 157 | | #[repr(C)] ... | 161 | | } 162 | | } | |_____^ | = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error: aborting due to 4 previous errors

error: could not compile nsstring. warning: build failed, waiting for other jobs to finish...

2.

make[1]: [/home/aj/.cache/yay/waterfox-classic-git/src/Waterfox/client.mk:419: realbuild] Error 2 make[1]: Leaving directory '/home/aj/.cache/yay/waterfox-classic-git/src/Waterfox' make: [client.mk:170: build] Error 2 ==> ERROR: A failure occurred in build(). Aborting...

any help would be greatly appreciated! New to Arch and very keen to get my beloved Waterfox back!

ilikenwf commented on 2019-08-11 00:10

You'll have to rebuild against the new lib. I'll bump the package when I get a chance.

zachir commented on 2019-08-10 18:24

As of today, running waterfox gives me the issue "libevent-2.1.so.6: cannot open shared object file." It appears libevent was updated and is needed by waterfox, so whenever you get a chance fixing that would be appreciated. The included library is now libevent-2.1.so.7

ilikenwf commented on 2019-07-19 20:02

Keep a copy of the entire build and source files on your local drive, ideally...the build system will then only rebuild that which needs rebuilt each iteration.

I think makepkg has a shallow option but I keep everything in a folder and thus don't just build and nuke the source files immediately like yaourt and pacaur do.

guitaristtom commented on 2019-07-19 18:00

Would we be able to add in --depth=1 in to the git clone? Having to clone so much with every small update tends to hurt. At least with the depth being set to 1 it'll only grab what is currently on master and not the entire history of the package.