Arch Linux User Repository

Binary version of this package is available on my repository on OBS and language packs are available as separete waterfox-classic-i18n-* packages.

Source files at: https://build.opensuse.org/package/show/home:hawkeye116477:waterfox/waterfox-classic-kpe.

Download at: https://software.opensuse.org//download.html?project=home%3Ahawkeye116477%3Awaterfox&package=waterfox-classic-kpe .

If you got 404, then temporarily try to replace download.opensuse.org with downloadcontent.opensuse.org. That should enforce direct download without mirror.

two items:

PKGBUILD line 231 should be : install -Dm644 $srcdir/waterfox-classic-kpe.1 \ "$pkgdir/usr/share/man/man1/waterfox-classic-kpe.1"

(fails because cannot stat waterfox-classic.1)

second, please warn that you renamed /usr/bin/waterfox to waterfox-classic. not a biggie but it was weird :-)

also, still cant build on rust 1.1.39 and clang/llvm 9.0.0 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

newer versions through errors while compiling https://paste.artixlinux.org/27253548

@toxygen KPE means KDE Plasma Edition :-)

shouldnt that be waterfox-classic-kde ?

This is Classic. I'll rename it and also push waterfox-current-kpe.

@toxygen There is no waterfox beta upstream any more.

Names and versioning changed since this month. There are now two different "stable" versions(Waterfox classic and waterfox current), based on different Firefox versions (legacy and modern). And versioning changed for both to YY.MM.X https://github.com/MrAlex94/Waterfox/wiki/Versioning-Guidelines

So if this is the legacy version it should be named waterfox-classic, as is not possible to distinguish classic from current based on version number.

@ranger - there is a waterfox-kde-beta which i believe is "current" so this would be classic dont know why the version changed to 2019-10 rather than the 5x.xx we had before

Is this Waterfox Classic or Current? Could help if you include in the name or description

@Star-X

rm src/path, or rm the whole src before makepkg

are you using the -e option?

Can't build currently, as the pkgbuild tries to do mkdir path and fails because path already exists.

Any fix?

well it goes through the [compile] portion fine, it gets to the [misc] portion, it buils some tests apparently, and gets to

waterfox-kde/src/Waterfox/build/unix/elfhack/test-ctors.c and fails:

9:40.49 Stack dump: 9:40.49 1. <eof> parser at end of file 9:40.49 2. Code generation 9:40.49 3. Running pass 'Function Pass Manager' on module 'waterfox-kde/src/Waterfox/build/unix/elfhack/test-ctors.c'. 9:40.49 4. Running pass 'X86 DAG->DAG Instruction Selection' on function '@test' 9:40.52 Stack dump: 9:40.52 1. <eof> parser at end of file 9:40.53 2. Code generation 9:40.53 3. Running pass 'Function Pass Manager' on module '/home/trumpop/waterfox-kde/src/Waterfox/build/unix/elfhack/test-array.c'. 9:40.53 4. Running pass 'X86 DAG->DAG Instruction Selection' on function '@test' 9:40.55 #0 0x00007f47d08b2b7b llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/usr/bin/../lib/libLLVM-9.so+0xb08b7b) 9:40.55 #1 0x00007f47d08b0a44 llvm::sys::RunSignalHandlers() (/usr/bin/../lib/libLLVM-9.so+0xb06a44) 9:40.55 #2 0x00007f47d08b0bd6 (/usr/bin/../lib/libLLVM-9.so+0xb06bd6)

with a bunch of other messages followed by

9:40.55 #20 0x00007f47cf4d21d8 clang::EmitBackendOutput(clang::DiagnosticsEngine&, clang::HeaderSearchOptions const&, clang::CodeGenOptions const&, clang::TargetOptions const&, clang::LangOptions const&, llvm::DataLayout const&, llvm::Module*, clang::BackendAction, std::unique_ptr<llvm::raw_pwrite_stream, std::default_delete<llvm::raw_pwrite_stream> >) (/usr/bin/../lib/libclangCodeGen.so.9+0xc51d8) 9:40.55 clang-9: error: unable to execute command: Segmentation fault 9:40.55 clang-9: error: clang frontend command failed due to signal (use -v to see invocation) 9:40.55 clang version 9.0.0 (tags/RELEASE_900/final) 9:40.55 Target: x86_64-pc-linux-gnu 9:40.55 Thread model: posix 9:40.55 InstalledDir: /usr/bin 9:40.55 clang-9: note: diagnostic msg: PLEASE submit a bug report to and include the crash backtrace, preprocessed source, and associated run script.

9:40.58 clang-9: note: diagnostic msg: PLEASE submit a bug report to and include the crash backtrace, preprocessed source, and associated run script. 9:40.60 clang-9: note: diagnostic msg: 9:40.60 **** 9:40.60 9:40.60 PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: 9:40.60 Preprocessed source(s) and associated run script(s) are located at: 9:40.60 clang-9: note: diagnostic msg: /tmp/test-ctors-c12089.c 9:40.60 clang-9: note: diagnostic msg: /tmp/test-ctors-c12089.sh 9:40.60 clang-9: note: diagnostic msg: 9:40.60 9:40.60 *** 9:40.60 make[5]: [waterfox-kde/src/Waterfox/config/rules.mk:791: test-ctors.o] Error 254 9:40.60 make[5]: Waiting for unfinished jobs.... 9:40.63 clang-9: note: diagnostic msg: 9:40.63 ***** 9:40.63 9:40.63 PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: 9:40.63 Preprocessed source(s) and associated run script(s) are located at: 9:40.63 clang-9: note: diagnostic msg: /tmp/test-array-bfb319.c 9:40.63 clang-9: note: diagnostic msg: /tmp/test-array-bfb319.sh 9:40.63 clang-9: note: diagnostic msg:

that's all. I wondered if some march or mtune settings are causing this? I have a ryzen 3700x (zen2) so maybe the cpu is conflicting there? i believe clang/llvm 9 have native support for ryzen (march=zenver2) so i switched those, and it fails at the exact same point. both test-ctors.c and the following file waterfox-kde/src/Waterfox/build/unix/elfhack/test-array.c fail with the same errors, both in the same folder waterfox-kde/src/Waterfox/obj-x86_64-pc-linux-gnu/build/unix/elfhack

and like i said, downgrading clang/llvm to previous versions, it builds just fine